The November 2025 release of Data Governance and Catalog includes the following changed behaviors.
Data access management operations now use the Data Access Management Agent service associated with the connection
Whenever Data Governance and Catalog pushes down a data access control policy or data filter policy to your cloud data platform, it now uses the Data Access Management Agent service configured in the runtime environment that is associated with the connection.
Previously, Data Governance and Catalog used any Data Access Management Agent service.
Increased sensitivity levels for data classifications
You can now customize up to 10 sensitivity levels for data element classifications in Metadata Command Center. Configure sensitivity labels on the Customize page and update the associated data classifications on the Explore page. Data Governance and Catalog shows the new sensitivity labels on assets when you update the data classifications.
Previously, you created up to five sensitivity levels for a data element classification.
For more information about customizing sensitivity levels for data classifications, see Asset customization.
Enhancement to export and import of asset relationships
If you include relationships while exporting assets, you can export relationships that have a business source asset and a technical target asset. Similarly, you can import relationships whose source is a business asset and target is a technical asset in template files for relationships.
The following table lists the relationships between asset types for which you can run Import and Export jobs:
Source Asset Type
Target Asset Type
Relationship Type
Policy
Data Set
is Regulating
Policy
Data Element
is Regulating
Process
Data Set
is Related to
Process
Data Element
is Related to
Project
Data Set
is Related to
Project
Data Element
is Related to
AI Model
Resource
is Used in
AI Model
Data Process
is Used in
Data Set
AI Model
is in Direct Lineage with
System
Resource
is Derived from
System
Data Source
is Derived from
Manual Data Element
Data Element
is in Manual Lineage with
Previously, you exported and imported relationships exclusively between business assets.
For more information about the bulk import process, see Bulk import process.
Data quality enhancement
You can now preview and download up to 1,000 failed rows from a rule occurrence.
Previously, you could preview up to 100 failed rows. You could not download the failed rows from a rule occurrence.
Display updated data quality scores for an asset
If you update data quality scores through API, bulk import, or data profiling, the updated data quality scores can take up to one hour to reflect in the Total Runs Table of the Score tab of a rule occurrence.
Previously, you could see the updated data quality scores in real time.
Changes to Tasks Inbox
You can no longer use the Name field to sort the Tasks grid on the Tasks Inbox page.
Users, roles, and groups no longer require the Read privilege to create and manage workflow tickets.
Automatic synchronization of glossary updates to technical assets
When you link a technical asset to a glossary asset so that the technical asset obtains its name and description from the glossary asset, Data Governance and Catalog can automatically update the technical asset details if the name or description of the glossary asset changes.
Previously, changes made to the glossary names and descriptions were not automatically reflected in the associated technical assets.
Connection permissions required for catalog source jobs
For catalog sources that require a connection in Administrator, or include a capability that needs a connection, you now need to have permissions on connections to perform the following tasks:
•Create or edit a catalog source
•Configure a catalog source to run on a schedule
•Manually run a catalog source job
This applies to all types of connections, such as source, staging, and flat file connections.
To run a catalog source job for catalog sources that reference other source systems, you need permissions on the connections for all the reference source systems.
Previously, you didn’t need permissions on connections to perform these tasks.