> ## Documentation Index > Fetch the complete documentation index at: https://docs.lovable.dev/llms.txt > Use this file to discover all available pages before exploring further. # Manage connectors in your workspace > Workspace admins control who can create connections and clients for each connector, which is also how connectors are made available or disabled. Learn the defaults per plan and every governance setting. Workspace admins and owners govern connectors in two places: * [**Connectors → Admin settings**](https://lovable.dev/dashboard?connectors) controls each connector type: who can create connections and clients for app + chat and app user connectors, and which chat connectors (MCP servers) are enabled. The admin settings area is available on **Business and Enterprise** plans. * [Privacy & security](https://lovable.dev/settings/privacy-security) (**Settings → Security → Privacy & security**) holds workspace-wide switches for MCP-based features, such as chat connectors (MCP servers) and local desktop MCP servers. One thing does not live in **Admin settings**: who can use an individual connection. Whoever creates a connection chooses who can use it, on any plan, as described in [Who can use connections and clients](#who-can-use-connections-and-clients). ## Default connector availability by plan Each connection type starts with a default availability that depends on your plan: | Connection type | Free, Pro, and Business | Enterprise | | :---------------------------------------------------------- | :------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------- | | App + chat connectors | Available by default | Effectively disabled: [Who can create connections and clients](#who-can-create-connections-and-clients) defaults to **No one** until an admin changes it | | Chat connectors (MCP servers), including custom MCP servers | Enabled by default | Enabled by default | | Local desktop MCP servers | Enabled, with no workspace switch on Free and Pro (the switch to turn them off is available on Business) | Disabled by default until an admin enables them | ## App connector controls Two connection types run through your app, and admins govern them the same way: * With [app + chat connectors](/integrations/app-connectors), a workspace member creates a **connection**: they sign in to the tool once (or paste an API key), and every project linked to the connection shares that account. * With [app user connectors](/integrations/app-user-connectors), a workspace member creates a **client**: the provider app registration that lets each user of the published app sign in with their own account. The client holds no user data itself; it's what makes the individual sign-ins possible. Each has its own tab in Admin settings: **Connectors → Admin settings → App + chat connectors** and **Connectors → Admin settings → App user connectors**. The controls below work identically in both tabs. ### Who can create connections and clients On **Free and Pro** plans, any workspace member with the editor role or higher can create connections and clients. On **Business and Enterprise** plans, workspace admins and owners choose one of three options for each connector, and the setting doubles as the availability switch: * **No one**: nobody in the workspace can create new connections or clients, which effectively disables the connector. (Enterprise plan default) * **Admins**: only workspace admins can create new connections or clients. (Business plan default) * **Editors & admins**: any workspace member with the editor role or higher can create new connections or clients. Some connectors (Lovable AI, Stripe, Paddle, Shopify, and Supabase) can only be turned on or off for the workspace. Built-in backend (Cloud) availability is managed from the Cloud connector settings. Individual projects can pause or remove it from **Cloud tab → Overview → Advanced settings**, described in [Advanced settings](/features/advanced-settings#pause-cloud). ### Who can use connections and clients Access is set by whoever creates the connection or client, not necessarily an admin. When creating one, you choose who has access to it: * **Only you** (default): only the person creating it can use it and its associated data. * **Invite specific people**: only you and explicitly added workspace members can use it and its associated data. * **Invite entire workspace**: click **Invite entire workspace** to make it available to everyone in your Lovable workspace. The access list carries real project consequences, for connections and clients alike: * **Only people with access** can link the connection or client to a project. * Projects that use it can **only be shared with workspace members that have access** to it. You cannot invite people outside your workspace to connections or clients, which means any external collaborators will lose access to the project using them. * If someone without access tries to open a project that uses the connection or client, they will be blocked from accessing it. * You cannot link a connection or client to a project if doing so would remove the project owner's access. One extra note for app user connectors: end users of the published app are not workspace members, and none of these settings apply to them. They connect their own accounts inside the app itself, as described on the [app user connectors page](/integrations/app-user-connectors). Access works alongside the [Who can create connections and clients](#who-can-create-connections-and-clients) settings described above. For example, when a connector is set to **Admins**, non-admins can't create new connections or clients, but anyone an admin has explicitly granted access to an existing one keeps that access. Connection- and client-level access is **not enforced after publishing**. Once a project is published, the live app is accessible regardless of these access settings. ## Chat connector controls [Chat connectors (MCP servers)](/integrations/chat-connectors) are personal connections, so there is no access list to manage. As with the other types, admins decide which chat connectors are available, in two places: * **Connectors → Admin settings → Chat connectors** enables or disables individual chat connectors for the workspace. The table also includes a **Custom MCP** row ("Allow members to connect their own MCP servers") that governs all [custom MCP servers](/integrations/custom-mcp) as a group. Individual custom MCP servers that members have connected do not appear in the table. * [**Remote MCP connectors**](/features/privacy-and-security-settings#remote-mcp-connectors) in [Privacy & security](https://lovable.dev/settings/privacy-security) turns all chat connectors on or off for the entire workspace. If the Connectors page says chat connectors are disabled for your workspace, this setting is the reason. * [**Local desktop MCP servers**](/features/privacy-and-security-settings#local-desktop-mcp-servers) in [Privacy & security](https://lovable.dev/settings/privacy-security) allows members to use MCP servers running on their own machine through [Lovable Desktop](/integrations/desktop-app). It requires **Remote MCP connectors** to stay enabled, and it is off by default on Enterprise workspaces. ## FAQ Its [Who can create connections and clients](#who-can-create-connections-and-clients) setting is the likely reason. On Enterprise plans, app + chat connectors are effectively disabled at first: the setting defaults to **No one** until an admin changes it for each needed connector in **Connectors → Admin settings → App + chat connectors**, as shown in [Default connector availability by plan](#default-connector-availability-by-plan). On any plan, an admin may have set the connector to **No one** or **Admins** for the same effect. A workspace admin turned off [**Remote MCP connectors**](/features/privacy-and-security-settings#remote-mcp-connectors) in [Privacy & security](https://lovable.dev/settings/privacy-security). That single setting controls all chat connectors for the workspace, including custom MCP servers, and the Connectors page reports it as chat connectors being disabled. Ask an admin to turn it back on if your workspace should be using chat connectors. The **Connectors → Admin settings** area and the **Who can create connections and clients** options are available on Business and Enterprise plans. Choosing who can use a connection you create works on all plans.