Notifications

Notifications help you stay informed about the changes that matter most. They can be triggered automatically by key Catalog events or configured as custom notifications by Catalog administrators. Custom notifications provide the flexibility to monitor specific changes and ensure that the right stakeholders are informed — enabling you to track critical updates, maintain data quality, and respond with confidence.

For example, use notifications when you want to:

• Track ownership changes to key objects.
• Monitor data quality issues or important updates.
• Alert stewards to missing or incomplete information.

Built-in Catalog notifications

The Catalog includes several built-in notifications that are triggered automatically based on user activity and object changes.

• Interest-based updates
  Sent when an object is created, edited, or deleted. Interested parties are notified when Get notified about updates? is enabled for the associated Interest Type, helping them stay aware of changes relevant to their role or responsibility.

• Discussion mentions
  Triggered when you, or a user group you belong to, are tagged in a discussion. This brings relevant conversations to your attention and supports collaboration directly within the Catalog.

• Approval tasks
  Generated when a change to an object requires your approval. This enables you to track and complete governance tasks in a timely and structured way.

• Review cycles
  Triggered when an object reaches its scheduled review date. This prompts assigned reviewers to validate content regularly, helping to maintain the accuracy and reliability of data assets.

Creating a new notification

You can create notifications to define when and how users are informed about changes to Catalog objects, giving you greater control beyond the built-in notifications provided by the system. This requires Catalog administrator permissions.

To create a notification, click into the Admin widget on the homepage. Within an Object Type, open the Notifications tab, where you can view and manage existing notifications or create a new one.

The notification form is organised into the following sections:

General

• Name - A user-friendly name used to identify the notification within the application.
• System label - A unique identifier for the notification, typically used for internal or technical reference.
• Summary - A short description outlining the purpose of the notification, helping others understand when and why it is used.
• Enabled - Controls whether the notification is active. When enabled, the notification will be triggered based on its defined configuration.

Trigger

• Event - Defines the action that will trigger the notification, such as when an object is created, edited, or deleted.
• Send notification if an object meets the following conditions - Allows you to refine when a notification is sent by defining specific criteria. For example, you can trigger notifications only when certain fields or associations change, or when a field has a particular value. This helps ensure notifications remain relevant and aligned with your governance requirements.

Message

• Recipient - Defines who will receive the notification based on published Interest Types. This ensures notifications are delivered to the appropriate stakeholders assigned to the object.

  If the selected Interest Type has Get notified about updates? enabled, recipients may receive duplicate notifications — one from built-in Interest-based updates and another from this notification. Consider whether a new notification is required or if the existing behavior already meets your needs.

• Subject line - Defines the subject of the notification message.

• Body - Defines the main content of the notification.

  Both the subject line and body support dynamic placeholders, allowing you to include live object data directly in your notifications. By typing @, you can select from a list of available object fields, associations, interests, as well as default properties such as the object name and URL.

  This allows you to create notifications that are tailored, informative, and immediately actionable, ensuring recipients have the context they need without additional follow-up.

  Placeholders are resolved when the notification is sent. For example, using @Status will display the current value of the Status field (e.g. Active) in the delivered notification.

Viewing notifications

You can view notifications from both the Catalog inbox and the Data Studio inbox.

To open the Catalog inbox:

1. Click on the bell icon in the header.
2. Click on View notifications.

Within the Catalog inbox, you can filter notifications by category. Categories can be selected individually or in combination, allowing you to view related activity together where needed.

For example, applying the Catalog filter displays notifications for Catalog object changes - including those sent to interested parties when update notifications are enabled and those triggered by notifications configured on objects.