> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Plugins & Connections

> Connect your warehouses and databases, and control who can use each connection.

A **plugin** is an integration type, such as Snowflake or PostgreSQL. A **connection** is one instance of it, such as your production Snowflake account. One plugin can hold many connections.

The agent and your [notebooks](/docs/notebooks/sql-and-python.md) work with the data your connections reach.

## Available plugins

| Plugin | Kind | Sign in with |
| - | - | - |
| **Snowflake** | Data warehouse | Programmatic access token, username and password, or browser sign-in (OAuth) |
| **BigQuery** | Data warehouse | Browser sign-in (OAuth) |
| **Databricks** | Lakehouse | Personal access token, or browser sign-in (OAuth) |
| **Amazon Redshift** | Data warehouse | Host, database, user, and password |
| **PostgreSQL** | Database | Host, database, user, and password, with optional TLS |
| **MySQL** | Database | Host, database, user, and password |
| **ClickHouse** | Analytics database | Host, database, and user |
| **Trino** | Query engine | Host, catalog, and user |
| **Apache Druid** | Analytics database | Router URL, with optional HTTP basic authentication |
| **Tinybird** | Analytics database | API host and a workspace token |
| **Elasticsearch** | Search engine | URL, with an API key, a bearer token, or a username and password |
| **MongoDB** | Document database | Connection string, with optional username and password |
| **Apache Kafka** | Streaming | Bootstrap servers and service credentials, with optional Schema Registry and Kafka Connect |
| **dbt** | Transformation | A dbt project folder |
| **Airflow** | Orchestration | Base URL and an API token |
| **AWS** | Cloud | IAM Identity Center (SSO) |
| **Generic SQL** | Any SQLAlchemy database | A [SQLAlchemy database URL](https://docs.sqlalchemy.org/en/20/core/engines.html) |

Notebooks also include **DuckDB**, which needs no connection. Use it to query files and the notebook's own dataframes.

Curious about an integration we do not support? Email [contact@datalooma.com](mailto:contact@datalooma.com). We would love to hear what you want to connect, and it may already be on our roadmap.

> [card] [Custom integrations](mailto:sales@datalooma.com)
>
> Need Datalooma to reach a system that is not listed here, or one built in-house? We build custom integrations for enterprise plans.

## Add a connection

**1. Open Connections**

Click **Connections** in the sidebar, then **Add connection**.

**2. Choose who it is for**

Under **Who this connection is for**, choose **Just me** for a personal connection, or a team to share it with everyone on that team. Only team admins can add team connections.

**3. Configure it**

Pick the plugin and how to sign in, and fill in its details.

Every connection also needs a **Deployment tier**: **Production**, **Staging**, **Development**, or **Local**. It tells the agent how careful to be.

**4. Save**

Click **Save connection**. Datalooma checks the connection first and saves it only if the check passes.

## Personal and team connections

| | Personal | Team |
| - | - | - |
| Belongs to | You | A team |
| Who can use it | You | Every member of the team |
| Who manages it | You | The team's admins |

A team connection can work in one of two ways:

* **One shared login.** The admin enters the credentials once, and everyone on the team uses them. Members never see the secret.
* **Each member signs in.** With browser sign-in (OAuth), each member signs in through their browser, so their own warehouse permissions apply.

The **Connections** page groups connections under **Yours**, your organization's, and each team's.

> [!NOTE]
>
> **Sharing a workspace lends your connections.** People you [share a workspace](/docs/workspaces/overview.md#sharing) with can query data through your connections from its chats while they have edit access.

## Credentials

Credentials are stored on Datalooma's servers, never in your workspace files and never in the agent's context.

Datalooma connects to your systems as the connection's user. Whatever roles and grants your warehouse enforces still apply.

## Status and upkeep

Each connection shows its status, such as **Connected** with when it was last verified, **Sign in again**, **Update credential**, **Unreachable**, or **No access**.

From a connection's menu, you can:

* **Verify now** to check it again.
* **Edit…** to change its settings or credentials.
* **Remove…** to delete it. Removing a team connection removes it for all members.

## Related

> [card] [Agent & Tools](/docs/foundations/agent-and-tools.md)
>
> How the agent uses your connections, and what it may do with them.

> [card] [SQL and Python](/docs/notebooks/sql-and-python.md)
>
> Query a connection from a notebook.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.