> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dqlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Connect Prizm to Collibra to push data quality scores, measure results, and rule context to your catalog and pull domains, business terms, and data concepts back into Prizm.

## What is the Collibra integration?

The Collibra integration connects Prizm data quality monitoring to the Collibra data governance catalog. Prizm pushes asset and attribute scores, measure results, data quality rule logic, and AI-generated rule descriptions to Collibra, and pulls domains, business terms, and data concepts from Collibra into the Prizm semantics layer.

The integration runs through Prizm's shared catalog sync framework, so jobs, schedules, and logs work the same way as the [Alation integration](https://docs.dqlabs.ai/integrations/alation/overview.md).

## What this integration enables

| Capability | Description |
| - | - |
| **Push asset scores** | Pushes the table or view quality score to the matching Collibra asset. |
| **Push attribute scores** | Pushes the column quality score to the matching Collibra attribute. |
| **Push measure results** | Creates and updates Data Quality Metric assets in Collibra with score, passed rows, failed rows, total rows, threshold, result, and run completion date. |
| **Push rule context** | Pushes the data quality rule SQL, the AI-generated rule description, dimensions, and a link back to Prizm. |
| **Granular push control** | Asset, Attribute, and Measure pushes are controlled independently. Measures can be limited to Auto, Custom, or Semantics. |
| **Pull domains, business terms, and data concepts** | Imports these from the Collibra communities and domains you configure. Pulled items appear on the semantics page with source type "Collibra". |
| **Field mapping** | Choose which Prizm fields are written to which Collibra attributes. |
| **Scheduled sync** | Catalog sync jobs run on a schedule, with job status and logs available in Prizm. |

## Authentication

Prizm supports these authentication methods for Collibra:

* **Username and password**
* **OAuth 2.0 client credentials**
* **Vault**, to fetch credentials from a connected vault integration

## How Prizm finds the target Collibra asset

Prizm resolves the Collibra asset to update in this order:

1. **Collibra Asset ID custom field.** If you enter a **Collibra Asset ID** on a Prizm metric, that value is used first. Otherwise the ID on the Prizm asset is used. Prizm verifies that the asset exists and is accessible before writing.
2. **Automatic discovery.** When no ID is provided, Prizm searches Collibra using the configured community and domain together with the database, schema, table, and column names. The search must return exactly one match. If none is found, the item fails with an asset not found error, and other items in the same run continue.

Using the Collibra Asset ID custom field is the most reliable option when names in Collibra differ from names in your source.

## Workflow

1. An admin configures the Collibra connection and selects the communities and domains to use.
2. The admin enables the push options (asset score, attribute score, and measure results) and the pull options (domains and terms).
3. Prizm runs a catalog sync job on the configured schedule, or on demand.
4. Prizm resolves each target asset, then creates or updates the Data Quality Metric assets and relations in Collibra. Writes are safe to retry.
5. The admin reviews job status, failures, and logs in Prizm.

## Prerequisites

* A Collibra instance URL
* A standard Collibra service user (not an admin account) with permission to read and write assets, and to create Data Quality Metric and Dimension assets in the Rulebook and dimension domains
* The Collibra community, domains, and Data Quality Metric asset type already created. Prizm doesn't create these
* The Collibra communities and domains to pull from, and the Rulebook and dimension domains to push to
* Admin or privileged user access in Prizm to configure integrations

> [!NOTE]
>
> To see pushed scores on the native Quality page of tables and columns in Collibra, configure Quality Score Aggregation in Collibra first (Settings → Operating Model → Quality Score Aggregation). Without it, Prizm still pushes to the Data Quality Metric assets.

> [card] [Setup](https://docs.dqlabs.ai/integrations/collibra/setup.md)
>
> Connect Collibra to Prizm, configure push and pull, and schedule syncs.

> [card] [Alation integration](https://docs.dqlabs.ai/integrations/alation/overview.md)
>
> Another catalog integration that uses the same sync framework.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.