Skip to content

You are viewing documentation for Immuta version 2.8.

For the latest version, view our documentation for Immuta SaaS or the latest self-hosted version.

SQL Access Pattern

Audience: Data Users

Content Summary: This section details the use cases of the Immuta SQL connection - with data sources, analytic tools, and projects - and illustrates SQL account management, data access, policy enforcement, and SQL best practices.

SQL Connection Use

Data Sources

Once subscribed to a data source, one of the mechanisms the user has for accessing data in that source is the Immuta SQL connection. The connection is a regular PostgreSQL connection, and the data sources look like PostgreSQL tables, but these tables abstract the true underlying database technology, allowing users to visit a single place for all of their data. However, the data still resides in its original location, not within Immuta. When a user queries the Immuta database, the query is transformed to sync with the underlying storage technology (e.g., Oracle, MSSQL, etc.) for any data source. When the data is returned from the original location, Immuta applies policies based on the querying user's attributes and forwards the data on to that user.

Analytic Tools

Users can hook their SQL connection to their favorite analytic tool, such as Excel, Tableau, RStudio, etc. For more information, see Analytic Tools.


To access data sources in the context of a project, Immuta users can also obtain unique SQL credentials for each project that they are a member of. See Creating Project Based SQL Connections for more information.

Section Contents