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

# Connector governance

> Control connector access in your Workspace with account ownership, people and groups, provider scopes, Agent permission limits, and shared account settings.

Connector governance controls which accounts your Workspace connects, who can use them, and how Agent uses that access.

> [!NOTE]
>
> This reference covers the early-access integration settings. Available
> controls depend on your Workspace, your permissions, and the integration. If
> your settings show **All integrations** instead of **Discover integrations**,
> see [Manage connectors](https://docs.replit.com/replitai/managing-connectors.md).

## Where to find the controls

Select the intended Workspace, then open **Settings > Integrations**. The updated settings have these views:

| View | What it contains |
| - | - |
| **Discover integrations** | Available services and their setup options. A service can have several configurations. |
| **Your integrations** | Configurations and accounts available to you, login actions, and your default permission choices. |
| **Workspace integrations (admin)** | Workspace configurations, their audiences, settings, and connected projects or chats. This view requires Workspace admin access. |

Members with **Can manage** access can manage an individual configuration from **Your integrations** without access to the admin view.

A **configuration** defines the setup for a service, including its account type, provider settings, and audience. A **connection** is an account connected through that configuration.
The **Configuration name** identifies each setup when a service has several configurations, such as separate development and production accounts.
Saving a configuration does not always connect an account. Personal configurations require each member to log in afterward.

## Account type and protocols

Setup offers only the combinations the integration supports. The account type determines whose credentials the connection uses.

| Account type | Behavior |
| - | - |
| **Personal** | Each member connects their own provider account. Sharing the configuration does not share one member's credentials with everyone. |
| **Shared** | Members use the same connected provider account, subject to its access grants and consent. |
| **Service account** | A dedicated, non-human account supplies the credentials. Availability depends on the provider. |

Protocols determine how the integration is used. **MCP** supports Agent conversations, **HTTP** supports apps and automations, **Git** supports repositories, and **Database** supports database access.
Not every integration offers every protocol. Some protocols require a separate configuration and authorization flow.

## Audience and roles

**Who has access** determines who can use the configuration. You can choose **Everyone in workspace**, including future members, or **Selected people and groups**.

| Role | Configuration access |
| - | - |
| **Can use** | View the configuration and connect an account through it. Account consent and access checks still apply when a project or chat uses the connection. |
| **Can manage** | Use and edit the configuration, manage its audience, and remove it. |

Workspace admins retain management access, including when you choose selected people and groups. Removing one audience entry does not remove access granted through another group.

The **Audience** view lists saved recipients visible to you. It is not a complete calculation of every person's effective access.
For group membership and other grants, see [Groups and permissions](https://docs.replit.com/teams/groups-and-permissions.md).

## Provider configuration and scopes

**Replit defaults** uses Replit's configured provider app. **Custom** uses your own provider configuration where supported, such as an OAuth client or service endpoint.
The provider determines which fields are required. Stored credentials are not displayed in the editor.

**Connector scopes** determine which provider permissions a connection can request. Choose the scopes needed for the intended work.
Required scopes and scopes used by existing connections may be locked.

> [!NOTE]
>
> Existing OAuth connections keep their current provider permissions until they
> reconnect. Changing configuration scopes applies to new connections and
> reconnections.

Changing Agent's permission mode does not add provider scopes. **Always allow** cannot grant access that the connected account lacks.

## Agent permission choices and Workspace limits

**Default permission** is your saved choice for a connection. **Workspace Agent Permission Limits** are admin controls that restrict Agent use across the Workspace.
For interactive Agent actions that support approval, the modes have these meanings:

| Mode | Meaning |
| - | - |
| **Always ask** | Ask before reading or changing data. |
| **Decide for me** | Ask for actions detected as potentially dangerous. This is not a promise to ask before every write. |
| **Always allow** | Read and make changes without an approval prompt, within the connection's existing access. |
| **Disabled** | Block use covered by that permission setting. |

> [!WARNING]
>
> During early access, some default-permission selectors state that they only
> save a preference and do not change Agent behavior. Do not rely on those
> selectors to require approval. Use the available access controls and provider
> permissions to restrict sensitive data or actions.

The Workspace limit section appears below **Your integrations**. Admins can set **All integrations** and individual connector limits.
An individual connector limit cannot loosen a stricter Workspace-wide limit. Members can choose a stricter setting where the permission control is enforced.
Policy changes apply to subsequent checks, including those made by running Agents.

For custom MCP servers, an **MCP origin override** applies to the server's origin: its scheme, host, and port.
Different paths on the same origin share that limit. **No limit**, where offered, removes that override without removing the Workspace-wide limit.

These controls do not make an app or unattended run display an interactive approval prompt.
A **Workspace Rep** is an Agent with its own access grants. Reps use their own connection grants and do not inherit a member's personal default permission.
A **Disabled** Workspace limit still blocks their use.

## Agent instructions

**Agent instructions** adds guidance for using a configuration, such as which channels to use or how to format records.
These instructions take precedence over the connector's instructions when they conflict, but they do not grant additional access.

Instructions are guidance, not a substitute for audience restrictions, provider scopes, or enforced permission limits.
Keep credentials in the provider's credential fields, not in Agent instructions.

## Accounts and credential changes

The available actions depend on the account type and your permissions:

* **Log in** or **Connect** creates an account connection through the saved configuration.
* **Reauthorize** renews the provider authorization when supported.
* **Edit public settings** keeps stored credentials while updating the visible configuration fields.
* **Replace credentials** requires the complete replacement credentials for the same provider account. Stored secrets remain hidden.

Where the editor distinguishes **Development** and **Production**, check the selected environment before replacing a shared account's credentials.
If a save is unconfirmed, use the displayed retry action to continue that attempt. Follow a reload or restart instruction when the page requests it.

## Status and connected projects

A saved configuration can exist without a connected account. **Account connected · health not checked** means an account is saved, without a live health result.
A **Last checked** time refers to a recorded result, not a guarantee that the provider is reachable now.

The **Connections** view shows visible projects, published projects, chats, or Reps attached to a configuration.
This is a list of current connections, not a provider-account list or a historical usage log.

## Logout, shared disconnect, and removal

These actions have different effects:

| Action | Effect |
| - | - |
| **Log out** | Deletes the selected saved personal connection. It does not revoke authorization with the provider. |
| **Disconnect shared account** | Removes that shared connection. Everyone using the account loses access, but the configuration remains. Provider authorization is not revoked. |
| **Remove configuration** | Deletes the configuration and its connections. Connected apps and chats lose access. It does not delete the provider account or provider data. |

To revoke authorization at the provider, use that provider's account or app settings.
Review the affected account and configuration before confirming removal.

## Related documentation

* [Manage connectors](https://docs.replit.com/replitai/managing-connectors.md) covers general integration setup and availability.
* [Groups and permissions](https://docs.replit.com/teams/groups-and-permissions.md) explains Workspace membership and access grants.
* [Connect via MCP](https://docs.replit.com/build/connect-via-mcp.md) covers custom MCP server setup.
