Data Sources in Immuta
Last updated
Was this helpful?
Last updated
Was this helpful?
Data owners expose their data across their organization to other users by registering that data in Immuta as a data source. When data is registered, Immuta does not affect existing policies on those tables in the remote system (unless an existing global policy in Immuta applies to the data source), so users who had access to a table before it was registered can still access that data without interruption.
When data sources support nested columns, these columns get parsed into a nested Data Dictionary. Below is a list of data sources that support nested columns:
S3
Azure Blob
Databricks sources with
When complex types are enabled, Databricks data sources can have columns that are arrays, maps, or structs that can be nested.
There are various roles users and groups can play relating to each data source. These roles are managed through the members tab of the data source. Roles include the following types:
Owners: Those who create and manage new data sources and their users, documentation, and .
Subscribers: Those who have access to the data source data. With the appropriate data accesses and attributes, these users and groups can view files, run queries, and generate analytics against the data source data. All users and groups granted access to a data source have subscriber status.
Experts: Those who are knowledgeable about the data source data and can elaborate on it. They are responsible for managing the data source's documentation and tags and descriptions.
See for a tutorial on modifying user roles.
The data dictionary provides information about the columns within the data source, including column names and value types.
Dictionary columns are automatically generated when the data source is created. However, data owners and experts can and .