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

# Connect with organization credentials

> Add a connector using credentials your organization stores in the Vault, so you can connect without entering client IDs, secrets, or API keys.

If your admins have added credentials for a connector to the Vault, you can connect through them instead of setting up your own app or key. You don't need to open the Vault or know the secret — DeepMask uses it on your behalf.

## Connect through the Vault

**1. Add the connector**

Open **Connectors** and choose the connector you want to add — for example Salesforce, Microsoft, Bright Data, 2slides, or a Custom MCP server.

**2. Choose the connection source**

If your organization offers credentials for this connector, DeepMask asks you to choose:

* **Organisation connection** — uses the credentials your organization manages. You don't enter any credentials.
* **My own credentials** — set up the connector with your own app or key, as usual.

**3. Pick the organization connection**

If your organization offers more than one connection for this connector — for example a production and a sandbox environment — choose the one you need. Use the name and description to tell them apart.

**4. Finish connecting**

* For **Salesforce** and **Microsoft**, sign in with your own work account. You only see and change data your own account can access.
* For **Bright Data**, **2slides**, and **Custom MCP servers**, the connector is ready right away. You share your organization's key, and you don't enter a server URL.

Your new connector appears under your connections with the **Organisation connection** badge and the name of the Vault secret it uses.

> [!NOTE]
>
> If the connector goes straight to the normal setup, your organization hasn't added credentials for it, or you aren't on the secret's access list. Ask an admin if you expected an organization connection.

## Switch between organization and your own credentials

You can't edit the credentials of a connector that uses an organization connection. To switch:

1. Delete the connector from your connections.
2. Add it again and choose the other connection source.

## When you need to reconnect

Your connector shows **Reconnect** when its organization connection can no longer be used as is. This happens when an admin:

* Disables or deletes the Vault secret.
* Removes you, or a group you belong to, from the secret's access list.
* Replaces the credentials with a different app or tenant.

It also happens if you leave the organization. Reconnect through another organization connection, if one is offered, or with your own credentials.

> [!NOTE]
>
> Changes take effect at your connector's next sign-in or token refresh, not instantly. A connection that was signed in before the change may keep working for up to about an hour, or longer for Salesforce sessions.

## Troubleshooting

> [accordion] That organisation connection is no longer available to you
>
> The secret was disabled or deleted, or your access was removed while you were connecting. DeepMask refreshes the list of available connections. Choose another one, or use your own credentials.

> [accordion] Your organization's policy blocked this connection
>
> Microsoft or Salesforce refused the sign-in because of a policy in your organization's account — for example, the app needs admin consent or you aren't assigned to it. Retrying won't help. Ask your admin to grant consent or give you access in Microsoft Entra or Salesforce.

> [accordion] This connection uses your organization's credentials and can't be changed here
>
> Connectors that use an organization connection are managed by your admins. Delete the connector and add it again to use your own credentials instead.

> [accordion] Organisation connections are not available on this server
>
> The Vault isn't set up for your workspace. Use your own credentials, or contact your admin.

## Related pages

> [card] [MCP connectors](https://documentation.deepmask.io/features/mcp-connectors.md)
>
> All connectors available in DeepMask.

> [card] [Vault overview](https://documentation.deepmask.io/vault/overview.md)
>
> What the Vault is and how it works.


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