Settings 
icon and click **Integrations**.\ :chevrons-right: The Integrations page opens.
{% endstep %}
{% step %}
In the upper right corner, click **Add Integration**.\ :chevrons-right: The Integration Setup wizard appears.
{% endstep %}
{% step %}
On the **Credentials** step, enter the required information.
| Option | Description | Required |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Service Type | 
Yes |
| Authentication Mode | The method of authenticating the API call to Collibra Platform.
You can select either Basic or OAuth.
To change the authentication mode, you should update the existing service URL credential. Only one integration credential can use a specific service URL. You can't have both Basic and OAuth for one service URL.
Yes |
| OAuth Token Endpoint | The Collibra Platform URL where Data Quality & Observability (self-hosted) sends requests to obtain the OAuth access token. The OAuth Token Endpoint must be in this format:https\://\
To manage the scope of the DGC resources to which OAuth can grant access during the integration, a new OAuth parameter in the Web ConfigMap is now set to DQ\_DGC\_OAUTH\_DEFAULT\_REQUEST\_SCOPE: "dgc.global-manage-all-resources,dgc.view-all" by default.
To register your Collibra DQ instance, see the OAuth Applications settings page.
| Yes
Required when using OAuth as the authentication mode.
Yes
Required when using Basic as the authentication mode.
Yes
Required when using Basic as the authentication mode.
Yes
Required when using OAuth as the authentication mode.
Yes
Required when using OAuth as the authentication mode.
, then **Run** to create an automatic mapping between the schemas within your selected Collibra DQ database and the schemas within Collibra Platform. If this is not the first integration, then proceed to the next step.
{% hint style="warning" %}
Only schemas ingested in Collibra Platform return when you click Run.
{% endhint %}
{% endstep %}
{% step %}
When the connection loads, click , then **Show Full Mapping** to expand the entire database mapping, including schemas, tables, and columns. You can use the Auto Map feature or manually map (or a combination of both) for each schema.
{% stepper %}
{% step %}
Auto Map
Click, then **Auto Map**. Select the tables to include in the mapping. Use the Search options to filter the results. Once the applicable tables are in the Included column, click **Apply Auto Map** to map tables in your DQ schema to those in DGC automatically. You can track the mapping status or cancel an in-progress mapping on the Mapping Status step.
If auto map fails for a schema, then the Data Quality & Observability (self-hosted) mapping table is not updated. This is considered an atomic update, which is a series of operations that function as a single, indivisible unit. The operations either complete entirely or fail completely, ensuring that no partial states occur.
Manually map
1. In the **DGC Name** column, optionally click the drop-down list and select a different schema (
) to update the schema mapping.
When a name match cannot be made, a "Not Configured" message displays.
) appear across from them in the DGC Name column.
3. In the **DGC Name** column, click the drop-down list and select a different table to update the table mapping, if necessary.
4. In the **DQ Name** column, click the table name to expand the available columns.\ :chevrons-right: The selected schema expands to show the available columns, and their corresponding columns ( 
) appear across from them in the DGC Name column.
5. In the **DGC Name** column, click the drop-down list and select a different column to update the column mapping, if necessary.
**Hide mapping** (next to the **Enter DGC Database UUID** field) and then **Show mapping** to refresh the counts. If this doesn't resolve the issue, then verify your column or schema name doesn't have special characters.
{% endhint %}
1. Optionally, click , then **Delete Mapping** to delete all the mapping records for the specific schema, including data quality rules, columns, jobs, and asset table relations.
2. Optionally, click **Add New** to map another connection and then repeat this process.
{% endstep %}
{% step %}
Click **Next**.\ :chevrons-right: The Mapping Status step opens.
{% endstep %}
{% step %}
On the **Mapping Status** step, optionally review mapping details.
Mapping Status allows you to view mapping details, such as the number of available tables in a schema that are mapped and when a connection mapping fails.
| Column | Description |
|---|---|
| Connection Name | The name of the data source included in the mapping. |
| Schema Name | The name of the schema included in the mapping. |
| Status | The state of completion of the mapping. |
| Start Time | The time stamp, in yyyy-MM-dd hh:mm:ss format, of when the mapping began. |
| End Time | The time stamp, in yyyy-MM-dd hh:mm:ss format, of when the mapping stopped. |
| Tables Mapped | The number of tables that mapped out of the total tables available in the schema. The 3 numbers shown in x/y/z format represent:
There may be instances when x+y does not equal z. This occurs when tables from Collibra Platform aren't available because their metadata hasn't been ingested. When those tables are found through the Data Quality & Observability (self-hosted) connection, there is no attempt to map the tables or columns. The table is included in the total table count (z), but not in the partial or all column table counts (x or y). |
| Exception | When an error during the mapping occurs, a message describes the issue. If the error message is truncated, you can hover your cursor over it to view the full message in a tooltip. When an exception did not occur, the value in this column is N/A. |
| Actions | When a mapping job is in progress, a  option appears in this column to allow you to cancel the job if necessary. |
More information about out-of-the-box dimensions
| Dimension | Description | Out-of-the-box dimension assigned? |
|---|---|---|
| Accuracy | The degree to which data correctly reflects its intended values. Monitors associated with the accuracy dimension:
| No |
| Completeness | The percentage of cells in a column that contain values identified as actual values, null, or empty. Completeness refers to the percentage of columns that have neither EMPTY nor NULL values. Monitors associated with the completeness dimension:
| Yes |
| Consistency | The degree to which data contains differing, contradicting, or conflicting entries. Monitor associated with the consistency dimension:
| Yes |
| Validity | The degree to which data conforms to its defining constraints or conditions, which can include data type, range, or format. Monitor associated with the validity dimension:
| No |
| Duplication | The degree to which data contains only one record of how an entity is identified. Refers to the cardinality of columns in your dataset. Monitors associated with the duplication dimension:
| No |