Release notes for Collibra Platform Self-Hosted

The following updates help meet compliance requirements and improve integration with federal IT systems and Collibra products:

• Federal Information Processing Standards (FIPS) mode is now required on both the BaseOS and Application Layer. This ensures compliance with regulatory standards, enhances security by enforcing strong cryptographic algorithms, and standardizes security policies across all Collibra environments.
• Collibra now supports IPv6-only environments.

The AI model traceability feature (in preview) will soon be available for Azure AI Foundry. This feature:

• Automatically creates lineage between deployed AI models, foundational AI models, and AI agents, and the data connected to them.
• Automatically links your AI use cases to the deployed AI models they use, so that the models appear on AI Use Case asset pages.

AI model traceability will be available as of the 26 October, 2025 Edge release, which coincides with the CPSH 2025.10 Wave 2 release.

The Lifecycle management feature, which is already available for the AI Model and AI Use Case asset types (and child asset types), is now also available for the AI Agent asset type (and child asset types). You can now configure the lifecycle stages for AI Agent assets, which are then reflected in the Lifecycle tracker on AI Agent asset pages.

The global assignment for the AI Agent asset type (and child asset type Azure AI Foundry Agent) now have the following default asset statuses:

• Core path: Candidate, Under Review, and Accepted
• Other statuses: Rejected and Archived

• The Description attribute is now available for Data Product Port assets. By adding a description, you can make the purpose and usage of the ports easier to understand.
  If you haven't updated the out-of-the-box asset page layout for the Data Product Port asset type, the attribute is added by default. Otherwise, you can manually add it to the layout.

• The Output Ports Viewer widget is now available for Data Product assets. This widget shows Data Product Ports with the relation "is output port for" the data product and the hierarchy of schemas, tables, and columns for a selected Data Product Port.
  If you haven't updated the out-of-the-box asset page layout for the Data Product asset type, the widget is added by default. Otherwise, you can manually add it to the layout.

• If sample data is enabled, it is now shown in Data Product assets. This helps users understand what to expect from the data product.

• Community offering workflows to simplify creating and building data products are added and updated in Collibra Marketplace:

  • Existing community offering workflows will be adapted to support the Data Product Port asset type.
  • Additional community offering workflows will become available:
    The "Promote to Data Product" workflow allows users to create a Data Product from a Data Set asset. It links the data exposed in a Data Set to a Data Product through a new or existing Data Product Port.
    The "Add port and output" workflow allows users to create a new Data Product Port or a new version of an existing Data Product Port from a Data Product.

With the new Notification Center, we improved the Notification settings, giving you more control over what you are emailed about, and how often.

• You can select specific types of notifications to receive by email, such as when an assessment is assigned to you or when someone replies to your comment.
• You can set the frequency of email notifications to:
  • Instantly
  • Daily
  • Weekly
  • Monthly (only for Resource changes)

• Comments you've been tagged in or replies to threads you've participated in.
  Note These were previously shown on the Mentions tab in your Profile settings.
• Assessments you've been assigned to.

The new Notification Center currently does not support any other notifications.

Notifications for identifying indirectly related policies and data categories are now available via the following communications tools. Enablement might be required.

• Email: Go to the “Edit the email notification settings” section in Manage a profile.
• Notification Center: Go to Notification Center.
• Slack: Go to About Slack integration.

• color: transparent;
• filter
• opacity
• pointer-events: none;
• position: fixed;
• position: sticky;
• visibility

• You can now use the Data Marketplace scope to further control when the "Add to Data Basket" button is available for assets. This restriction ensures that users, whether inside or outside Data Marketplace, can add only assets that meet the Data Marketplace scope (asset types, statuses, and organization) and the asset types configured in the Data Basket feature. To enable this, on the "Settings" page, go to "Search" → "Actions and Preview" → "Data Basket" and select the "Restrict to Data Marketplace scope" checkbox.
• The "Shopping basket" tab in "Search" → "Actions and Preview" is renamed "Data basket". The "Show Basket" checkbox on the "Data basket" tab is renamed "Define whether users can add assets to data basket and request access".
• You can now control whether the Data Set and Report asset types can be added to a data basket. These asset types are no longer automatically eligible.

We added the Databricks Volumes and Databricks Schema asset types. Additionally, the"Databricks Schema contains/is part of Databricks Volumes" relation type is added. These additions support the upcoming Databricks Unity Catalog integration operating model, which will be introduced in a future release.

Note Adding asset type groups to the Data Marketplace scope doesn't directly impact the search results in standalone Data Marketplace or Data Marketplace in Search. You need to still add the allowed asset types to the Data Marketplace scope on the "Asset Types" tab.

We added a new resource role, Control Manager. This role is specific to Control Tower, a new product which will be available in a future CPSH release. As such, this resource role is visible, but not yet functional.

The AI Model asset type is now renamed Deployed AI Model. We also added a new Foundational AI Model asset type. We did this to better reflect real-world distinctions between Foundational AI Models, which serve as versatile, pre-trained models, and Deployed AI Models, which are tailored and operationalized for specific use cases in production.

When you upgrade to Collibra 2025.09, all AI Model assets in your environment are automatically converted to Deployed AI Model assets.

The Deployed AI Model and AI Agent asset types (and child asset types) have migrated from the Business Asset Type category to the Technology Asset Type category. Existing AI Model assets (now Deployed AI Model assets) and AI Agent assets stored in Business Asset domains remain accessible. Custom asset types are not affected by this change; however, ensure that new assets can only be created in Technology Asset domains. Go to "Required actions” below.

We have also included a new out-of-the-box community named AI Governance. This new community comes with two domains:

• A Business Assets domain for your AI Use Case assets.
• A Technology Assets domain for your Deployed AI Model, Foundational AI Model, AI Project, and AI Agent assets.

Required actions

If you have any Deployed AI Model or AI Agent assets in Business Asset domains, you need to:

• Do one of the following:
  • Move all Deployed AI Model and AI Agent assets to a Technology Asset domain. For guidance, go to Manage assets.
  • Manually change the domain type to Technology Asset domain. For guidance, go to Manage domain types.
• For any custom child asset types of the Deployed AI Model and AI Agent asset types, ensure that new assets can only be created in Technology Asset domains. You need to configure this in the asset type assignments. For guidance, go to the section “Assign a domain type to an asset type” in the topic Manage assignments.
• If, prior to Collibra 2025.09, you were using an assessment template that has the asset type Business Asset associated with it, to assess an AI Model, an "asset type mismatch" error is now generated because the newly named Deployed AI Model asset type is not a child of Business Asset. To avoid this error, ensure that any assessment templates you use to assess Deployed AI Models are associated with the Deployed AI Model asset type or its parent Technology Asset type. For more information, go to Asset type in a template.

• You can now save an empty description.
• When editing a description, the current description text now shows instead of the latest unsaved edit.