Skip to main content

Asset Change Notification
App

The Asset Change Notification app monitors metadata activity in Atlan and sends alerts whenever assets are created, updated, or deleted. It gives teams real-time visibility into critical changes like description edits, owner updates, or tag modifications.

This reference page describes the complete configuration for Asset Change Notification. It defines the available properties, valid values, and configuration formats required to set up automated alerts for asset changes.

Access​

The Asset Change Notification app isn't enabled by default. To use this app, contact Atlan support and request it be added to your tenant.

Configuration​

This section defines the fields required for workflow setup.

Workflow name​

Specifies a unique and descriptive name to identify the workflow configuration in the Atlan interface. This name appears in the workflow list and helps distinguish it from other workflows, especially in environments where multiple change-monitoring workflows are set up.

Example:

prod-asset-change-notification

Asset type​

Defines the types of assets that are monitored for changes. Only assets of the specified types can be included in notifications. This enables you to restrict monitoring to the most relevant parts of your metadata ecosystem.

Provide the list of asset types in scope, separated by commas.

  • Example: If you want to track updates to tabular data assets:

    Table,View,Column

  • Example: If you want to monitor glossary changes for governance purposes:

    Glossary,GlossaryTerm

  • Example: If you want to capture process-level events:

    Process,AtlasGlossaryCategory

For the complete list of supported asset types, refer to the Atlan data model documentation.

Start date​

Specifies the initial date from which the workflow begins monitoring asset changes. This ensures that only events occurring on or after the configured date are included in the first run.

First run only

After the first execution, the workflow automatically uses the last processed date from the previous run, and the Start date value is no longer applied.

Action​

Determines the type of asset event that triggers notifications. This property controls the scope of changes the workflow monitors and exports. You must select a single option - creation, update, deletion, or a combination of creation and update based on your monitoring needs.

Asset created​

Select this option to capture only newly created assets in Atlan. A notification is generated whenever a new asset of the specified type (for example, a table, view, or glossary term) is registered.

The exported details typically include:

  • Asset type (for example, Table, View, Column, GlossaryTerm)
  • Qualified name
  • Display name
  • Creation timestamp
  • Associated metadata such as owners, tags, and certificate (if available at the time of creation)

Example: If a new table sales_transactions is ingested into your warehouse and registered in Atlan, it can appear in the created assets file with its metadata.

Asset updated​

Select this option to capture only updates made to existing assets in Atlan. A notification is generated whenever a monitored asset changes after its creation.

In addition to selecting this option, you must also define the event types you want to track. Event types represent the specific kinds of changes that can occur on an asset. One or multiple event types can be selected.

Available event types:

  • Description: when an asset’s description is created or updated.
  • alias: when an alias is added or updated.
  • Asset: when general asset properties are modified.
  • Announcement: when an announcement is created or updated.
  • Term: when a glossary term is linked or unlinked.
  • Owners: when owners are added or removed.
  • Tag Added: when a tag is directly applied to the asset.
  • Tag Removed: when a tag is directly removed from the asset.
  • Tag Added via propagation: when a tag is added to the asset through lineage propagation.
  • Tag Removed via propagation: when a propagated tag is removed.

Example: If the description of the customer_orders table is modified and a new tag PII is added, both changes are captured in the updated assets file, each recorded with its corresponding event type.

Asset deleted​

Select this option to capture assets that have been deleted from Atlan. A notification is generated whenever a monitored asset is removed, regardless of how or why it was deleted.

Unlike Asset updated, there are no event type options to configure, deletion is always treated as a single event.

The exported details typically include:

  • Asset type (for example, Table, View, Column, GlossaryTerm)
  • Qualified name (as last recorded before deletion)
  • Display name
  • Deletion timestamp

Example:
If the temp_staging_data view is removed from your catalog, it appears in the deleted assets file with its metadata as it was known prior to deletion.

Asset created & updated​

Select this option to capture both newly created assets and updates to existing assets. This configuration combines the functionality of Asset created and Asset updated into a single run, ensuring comprehensive coverage of new registrations and ongoing modifications.

When this option is selected, you must also specify which event types to track for updates. Creation events are always included by default.

Available event types for updates:

  • Description: when an asset’s description is created or updated.
  • alias: when an alias is added or updated.
  • Asset: when general asset properties are modified.
  • Announcement: when an announcement is created or updated.
  • Term: when a glossary term is linked or unlinked.
  • Owners: when owners are added or removed.
  • Tag Added: when a tag is directly applied to the asset.
  • Tag Removed: when a tag is directly removed from the asset.
  • Tag Added via propagation: when a tag is added to the asset through lineage propagation.
  • Tag Removed via propagation: when a propagated tag is removed.

Example: If a new glossary term Customer Lifecycle is added and the Churn Rate term has its definition updated, both can appear in the created and updated assets file.

Filters​

Filters define additional conditions that must be met for assets to be included in change notifications. These properties help refine monitoring so that alerts are limited to assets of specific interest, such as those with certain naming conventions, ownership, or governance status.

All filter properties are optional. If no filters are defined, notifications are generated for all assets of the selected type and action.

Qualified name prefix​

Restricts monitoring to assets whose qualified names begin with one or more specified prefixes. This filter is useful when asset identifiers follow a consistent naming pattern, such as environment, database, or schema prefixes. Multiple prefixes can be specified, separated by commas.

Example: If you want to monitor assets from multiple Snowflake schemas:

default/snowflake/1234567890/PROD/,default/snowflake/1234567890/STAGING/

Example: If you want to monitor assets from different environments:

default/snowflake/1234567890/PROD/,default/postgres/analytics/

Qualified name contains​

Restricts monitoring to assets whose qualified names contain specific substrings. This filter is helpful when assets of interest include consistent identifiers, such as project names or domain markers.

Example: If you want to monitor assets that belong to finance or staging environments:

finance,staging

Certificate​

Restricts monitoring to assets with a specific certificate status. This filter enables governance teams to target assets based on their certification state, ensuring that notifications focus on the right level of data quality and trust.

Select one or more of the available statuses if needed:

  • Verified: Indicates that the asset has been reviewed and approved as accurate and reliable.

  • Draft: Indicates that the asset is still being reviewed or prepared.
    Use this option when monitoring work-in-progress assets that may require closer oversight.

  • Deprecated: Indicates that the asset is no longer recommended for use.
    Use this option when monitoring assets flagged for retirement or removal.

Example: If you want to monitor only trusted assets that have been reviewed and approved:

Verified

Owner user​

Restricts monitoring to assets owned by specific users. Use this filter to notify stakeholders when assets under their responsibility are created, updated, or deleted. Multiple usernames can be specified.

Example: If you want to monitor assets owned by Alice and Bob:

alice,bob

Owner groups​

Restricts monitoring to assets owned by specific groups. This filter supports governance models where groups manage assets collectively, such as data engineering or analytics teams. Multiple owner groups can be specified.

Example: If you want to monitor assets owned by the Data Engineering and Analytics teams:

data-engineering,analytics-team

Tag​

Restricts monitoring to assets with specific tags applied. This filter is effective for targeting sensitive, critical, or categorized assets based on governance tagging policies. Multiple tags can be specified.

Example: If you want to monitor assets tagged as personally identifiable information (PII) or critical:

PII,Critical

Notification​

The notification configuration defines how information about created, updated, or deleted assets is delivered to stakeholders. This ensures that changes are communicated through the most suitable channel for your organization, whether by email, direct file access, or integration with cloud storage.

Regardless of the option selected, the workflow also generates .csv files for each run. These files are always stored in the tenant's associated Object store bucket under the path:

argo-artifacts/default/<workflow-run-name>/

The generated files include an entry for each event. If an asset is updated multiple times within the same period, each update is recorded as a separate entry.

Notification channel​

Choose the channel through which notifications are delivered.

Notifications are sent directly to specified users or groups via email. The asset change report is included in the email body and attached as a .csv file.

Email addresses​

Defines the list of recipients who receive the email notification. Multiple addresses can be entered, separated by commas.

Example: If you want to notify two individual users:

alice@example.com,bob@example.com

Atlan groups​

Defines the Atlan groups that receive the email notification. Multiple groups can be specified, separated by commas.

Example: If you want to notify the Data Engineering and Analytics groups:

data-engineering,analytics-team

Email subject​

Defines the subject line of the email notification. If left empty, a default subject line is used.

Example: If you want the email subject to clearly identify asset changes in production:

[Atlan] Asset Change Report - Production