Setup overview
Before you can start using Data Access, you need to set it up for your data source. The setup involves the following phases.
| Phase | Description |
|---|---|
|
1. Configure data source permissions |
Before connecting a data source to Data Access, configure the underlying data source with the necessary permissions to allow Data Access to synchronize the required information. Data Access requires broader permissions than standard Data Catalog ingestion, because it actively reads, creates, and updates access controls. |
|
2. Create data source connection |
To bridge Data Access and your underlying data source, create a connection from an Edge or Collibra Cloud site to the data source. Data Access requires specific connection types for certain data sources. It does not support standard JDBC connection types, which are typically used for Data Catalog ingestion. For example, for Databricks and Snowflake, you must use the dedicated Data Access connection types, Databricks Account and Snowflake, respectively. However, for BigQuery and Microsoft Entra ID, you can reuse the existing connection types, GCP connection and Azure connection, respectively. |
| 3. Add data source to Data Access |
Once your Edge connection is ready, add the data source to Data Access and link it to the data source connection. This is when you set the synchronization schedule to pull the existing entities from your underlying data source. Data Access does not require you to create an Edge capability; it automatically creates one when a synchronization is triggered. This Edge capability acts as the connector, running the synchronization instructions sent from Data Access to your underlying data source. If the capability is manually deleted from Edge, Data Access simply recreates it during the next synchronization. |
|
4. (Optional) Link data source to System asset |
To fully integrate your data governance landscape, optionally, link the data source to an existing System asset in Data Catalog. This phase is not applicable for Microsoft Entra ID and Okta. |
Related topics
- BigQuery
- Databricks
- Microsoft Entra ID
- Okta
- Snowflake