FAQ
What are connections?
Connections allow you to register your data objects in a technology through a single connection, making data registration more scalable for your organization. Instead of registering schema and databases individually, you can register them all at once and allow Immuta to monitor your data platform for changes so that data sources are added and removed automatically to reflect the state of data on your data platform.
What will change with connections?
There are three high-level changes:
Automatic table registration: All unregistered tables that the configured credentials have access to will be registered into Immuta in a disabled state. All tables and schemas under this connection with schema monitoring on will continue to be monitored with object sync.
Simplified table names: All data source names will now reflect the connection and hierarchy. If your tables were not already named this way, the names will be changed.
Fewer API endpoints: When this upgrade begins, a select number of data and integration API endpoints will be blocked for this connection and its tables. See the documentation, linked below, for a complete list of the impacted endpoints.
For a more in-depth look at the differences, see the Upgrading to a connection guide and Before you begin page.
How will connections affect my existing integrations?
Your integrations will continue to work throughout the upgrade process with zero downtime.
Post upgrade, some configuration options will now be part of the connection menu: credentials, enabling, and disabling. The Snowflake and Databricks Unity Catalog integrations will continue to be visible in the Integrations tab on the Immuta app settings page, but Trino integrations will only exist in connections.
How will connections affect my existing data sources?
All pre-existing data sources will continue to exist. If you have used a custom naming template, you will see names getting updated as the connection uses the information from your data platform to generate data source names.
How will connections affect my policies?
Connections do not impact any policies or user access in your data platform.
How will connections affect my users?
Connections will not affect your registered users or their access in your data platform.
However, Immuta administrators will see notable differences in the UI with a new Connections tab now being displayed.
Do I need to change my scripts running against the Immuta APIs if I want to use connections?
Most likely, since there are a number of API changes in regard to data sources and integrations. See the API changes guide for details about each affected API endpoint and the substitute.
Are the permissions required for the system user different with connections?
No, the Immuta system user still requires the same privileges in your data platform. See the Upgrading to a connection guide for more details.
What is going to happen with the integrations?
We recommend upgrading to connections as soon as possible due to their many benefits.
Legacy onboarding patterns will no longer be supported by the following dates and technologies:
September 2025: Databricks Unity Catalog and Snowflake
September 2026: Trino
Is my environment the right choice for the connections upgrade?
Connections support upgrading from legacy Snowflake, Databricks Unity Catalog, or Trino technologies. See the Upgrading to a connection guide for more details and reach out to your Immuta support professional if you are interested in the upgrade.
Last updated
Was this helpful?