Permissions - Precisely Data Integrity Suite

Data Integrity Suite

Product
Spatial_Analytics
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
Data Integration
Data Enrichment
Data Governance
Geo Addressing
Data Observability
Data Quality
Core Foundation
ft:title
Data Integrity Suite
ft:locale
en-US
PublicationType
pt_product_guide
copyrightfirst
2000
copyrightlast
2026

Metadata extraction from Databricks is always read-only. The process does not modify data but requires access to system tables to retrieve advanced metadata, such as the SQL definitions of views and stored procedures.

Permissions for operational lineage

To enable operational lineage tracking, your Databricks token must be generated with the following scopes: sql and unity-catalog. Tokens without these scopes cannot retrieve the lineage data needed for operational lineage features.

Your Databricks user must also have the following permissions:

USE CATALOG on system
USE SCHEMA on system.access
SELECT on system.access.column_lineage 

Required permissions

The user must have permission to run USE CATALOG, USE SCHEMA, and SELECT commands on the following catalogs, schemas, and metadata tables:

system.information_schema.metastores
system.information_schema.schema_tags
system.information_schema.table_tags
system.information_schema.column_tags
system.information_schema.catalog_tags
system.information_schema.catalogs
<catalog>.information_schema.schemata
<catalog>.information_schema.tables
<catalog>.information_schema.columns
<catalog>.information_schema.key_column_usage
<catalog>.information_schema.table_constraints
<catalog>.information_schema.referential_constraints
<catalog>.information_schema.key_column_usage
<catalog>.information_schema.table_constraints
<catalog>.information_schema.key_column_usage
<catalog>.information_schema.routines
<catalog>.information_schema.routine_columns
<catalog>.information_schema.routines
<catalog>.information_schema.views
<catalog>.information_schema.tables
where <catalog> is a specific catalog to import;