# Connections

> Part of the NocoDB documentation (Apps). Index of all pages: https://nocodb.com/llms.txt. Any docs page is available as Markdown by adding `.md` to its URL.

URL: https://nocodb.com/docs/apps/connections
Last updated: 2026-10-05

Connect a NocoDB app to external services through workspace integrations, with one shared account or each user's own account.

<AskNocoAI>
  <Prompt>
    Send a confirmation email through [Gmail] when a [booking] is created
  </Prompt>

  <Prompt>
    Let each user send messages from their own [Slack] account
  </Prompt>

  <Prompt>
    Read [orders] from our [Postgres] database
  </Prompt>
</AskNocoAI>

A NocoDB app uses **connections** to reach external services, for example an email provider, a chat tool or a database. Each connection the app needs is answered by an [integration](/docs/product/integrations) of the workspace. You manage them in **App Settings** → **Connections**: "The connections this app needs, and what answers each one."

<img alt="The Connections tab" src={__img0} placeholder="blur" />

## How the app gets a connection

1. You ask NocoAI for a feature that uses a service, for example "send a confirmation email".
2. NocoAI declares the connection that the app needs. It shows in **Connections this app needs**.
3. The app asks for access to a workspace integration. The request shows in **Pending requests**.
4. Click **Approve** to give the app access, or **Decline**.

You can also give access first. In **Available integrations**, find the integration and click **Grant access**. To add a new integration to the workspace, click **Browse integrations**.

## Connection types

Each connection that the app needs uses one of two types:

| Type                        | What it means                                                                                                                              |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| **One shared account**      | All people who use the app use the same account. For example, every email goes out from one company address.                               |
| **Each user's own account** | Each person connects their own account, and the app acts as that person. For example, each salesperson sends email from their own mailbox. |

For **Each user's own account**, turn off **Share credentials between users** on the integration. Each person then connects their own account when the app asks. When a person has not connected their account, the app does not use a shared account in its place.

## Manage connections

| To                                                | Do this                                                                          |
| ------------------------------------------------- | -------------------------------------------------------------------------------- |
| Connect a connection that shows **Not connected** | Click **Connect** and select an integration.                                     |
| Use a different integration                       | Click **Change**.                                                                |
| Add a connection                                  | Click **Add a connection**.                                                      |
| Stop the access of the app                        | Click **Disconnect**, or **Revoke** on a granted integration.                    |
| Remove a connection the app no longer needs       | Select **Remove connection**. "Actions that still use it must be deleted first." |

Connections marked **Optional** are not required for the app to work.

## Good to know

* Keep API keys and passwords in connections, not in the pages of the app. Visitors can download the code of pages. See [Public access](/docs/apps/public-access).
* In an [environment](/docs/apps/environments), each integration can use different settings, for example a test account in Staging.

## Availability

* Connections that use **One shared account** are available on all plans that include Apps.
* **Each user's own account** is available on the **Scale** plan and above.
* Actions that read external data through SQL, HTTP or Redis connections are available on the **Plus** plan and above.

## Related

* [Integrations](/docs/product/integrations)
* [AI app builder](/docs/apps/app-builder)
* [Data for apps](/docs/apps/data)

---

## Related pages

- [Apps](https://nocodb.com/docs/apps.md): NocoDB Apps is an AI app builder for creating enterprise-grade work apps: describe the app, and NocoAI builds it on the data you already have, with teams, permissions, an API and an MCP server.
- [Vibe Coding with NocoDB Apps](https://nocodb.com/docs/apps/vibe-coding.md): Vibe coding is making software by describing it to AI. NocoDB Apps bring vibe coding to enterprise-grade work apps, on your own data, with teams, permissions and safe deploys.
- [Create an App](https://nocodb.com/docs/apps/create-app.md): Create a NocoDB app with AI: describe the app, and NocoAI builds it on your data. Start from the App tile in a base, with Build with AI, or in the NocoAI chat.
- [AI App Builder](https://nocodb.com/docs/apps/app-builder.md): Build and change enterprise-grade work apps in NocoDB's AI app builder: describe a change to NocoAI in the chat, and test it in the live preview.
- [Data for Apps](https://nocodb.com/docs/apps/data.md): Build NocoDB apps on the data you already have: NocoDB tables, your own PostgreSQL or MySQL database, and data that syncs from tools such as GitHub and HubSpot, with no record limit.
- [Secure Vibe Coding](https://nocodb.com/docs/apps/security.md): How NocoDB Apps keep AI-built work apps safe: teams and action grants, record rules, reviewed public pages, secrets in connections, scoped API tokens, environments and version restore.
- [Members and Teams](https://nocodb.com/docs/apps/members-and-teams.md): Control who can use a NocoDB app and what they can do in it with app teams, members and action grants.
- [Public Access](https://nocodb.com/docs/apps/public-access.md): Make pages of a NocoDB app public, and choose which actions visitors can run without signing in.
