> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stefanbrain.com/llms.txt
> Use this file to discover all available pages before exploring further.
> ## Agent Instructions
> Follow the content contract in AGENTS.md.
> Treat text as the canonical explanation; video and screenshots enhance it.
> Do not publish unverified product behavior or duplicate an existing canonical article.
# Share connectors with your team
> Share one supported connected account, control member access and permission boundaries, and verify it from a teammate's Chat.
## What this article shows you
Share one supported connected account with your StefanBrain team without sending teammates the account login.
The person who connected the account keeps control of access, permissions, reconnects and disconnection.
## Practical use cases
Give analysts access to supported Meta read and analysis workflows while
**Can publish ads** stays off.
Let approved teammates work from the same ad, landing-page or company data
instead of separate exports.
Let teammates use a supported company account through StefanBrain without
distributing its credential.
Let another operator continue from the same company source while the
connection stays with its owner.
Keep both accounts available, then name the shared company account in the
request that should use it.
## Video walkthrough
## How team connector sharing works
Team access covers the connected provider account as a whole. It does not
add folder-level or resource-level limits inside that account.
Use a narrower company account when the full connected account contains more than the team should access.
| Control | Who controls it | What it changes |
| - | - | - |
| **Team access** | Connection owner | Makes the account available to teammates. Eligible members are included unless the owner excludes them. |
| Member switches | Connection owner | Excludes or restores one teammate without changing access for anyone else. |
| **Tool permissions** → **Team** | Connection owner | Sets what teammates can run for connectors that expose tools. This profile is separate from **You**. |
| **Can publish ads** | Connection owner | For Meta only, grants one teammate permission to publish through the shared Meta connection. It starts off for every teammate. |
| **Use in my chats** | Each teammate | Shows or hides that shared account in only that teammate's Chat connector picker. |
| Reconnect or disconnect | Connection owner | Repairs or removes the underlying connection. Teammates cannot perform either action. |
The credential stays server-side. A teammate uses the owner's connection without receiving its token.
For generic connector tools, reads without a separate Team setting inherit
the owner's effective permission. Writes without a Team setting become
**Needs approval**. Meta uses **Can publish ads** instead, and it starts off
for each teammate. Custom MCP connectors cannot be shared in this version.
## What you will do
1. Open the connected company account.
2. Turn on **Team access** and choose the teammates who need it.
3. Review Team tool permissions or Meta's **Can publish ads** setting.
4. Have a teammate turn on **Use in my chats**.
5. Verify the account with one predictable read.
## Before you start
* The owner and teammate must be active members of the same StefanBrain team.
* The account must be connected and show **Team access**.
* Prepare one company source with a result you already know.
## Follow along
Open **Connectors**. Under **Your connectors**, choose the exact company
account the team should use.
If **Team access** is missing, confirm that the connection belongs to you
and supports sharing. Custom MCP connectors do not.
Turn on **Team access**. Confirm the state changes to **Shared with team**
and the member list appears.
Leave the intended teammates on. Turn off access for anyone who should not
use this account. This does not affect other included teammates.
For a connector with **Tool permissions**, select **Team** beside **You**
and review the tools teammates may run.
For Meta, use the separate **Can publish ads** switch. Leave it off for
teammates who only need read and analysis access.
The teammate opens **Connectors**, finds the account under **Shared with
you**, and turns on **Use in my chats**. This changes only their own Chat
connector menu.
Open a Chat and enable the provider under **Connectors**. If personal and
shared accounts coexist, name the company account in the request.
```text theme={"system"}
Use the shared Glow Labs Drive account.
Find "Glow Labs campaign brief" and return the approved promise and audience note.
Read the document only. Do not change it.
```
Compare the response with the known document before using the connection
for a larger workflow.
## Verify the result
The owner should see **Shared with team** with the teammate enabled. The teammate should see **Shared with you**, have **Use in my chats** on, and receive the expected approved promise and audience note.
The teammate can now use the intended shared account from Chat. The provider
credential remains with the connection owner.
## Understand later changes
| Change | Result |
| - | - |
| A teammate turns off **Use in my chats** | The account leaves that teammate's Chat connector picker. Other teammates are unaffected. |
| The owner excludes one teammate | That teammate loses access immediately. The share remains active for other included members. |
| The owner turns off **Team access** | Every teammate loses shared access. The owner's provider connection remains connected. |
| The owner disconnects the account | The connection and its team share end. |
| The connection needs attention | Teammates see that only the owner can reconnect it. The owner must repair the connection. |
| A teammate leaves the team | Their effective shared access ends with their active membership. |
| The owner changes **Can publish ads** for a Meta teammate | That teammate gains or loses the ability to publish through the shared Meta connection. Their shared read and analysis access remains controlled by the separate member access switch. |
## Common mistakes and troubleshooting
Confirm that you opened your own connected account under **Your
connectors**. Custom MCP connectors do not support team sharing.
Confirm the teammate is active on the same StefanBrain team. Then check
**Team access** and their member switch.
The teammate turned off their own preference. Open the account under
**Shared with you** and turn on **Use in my chats**.
Personal and shared accounts can coexist. Name the shared company account
and source in the next request.
The Team permission is **Needs approval**, or no Team write permission is
set. Choose **Approve once** or ask the owner to change the Team setting.
**Can publish ads** starts off for every teammate. The connection owner
must enable it for that member.
Send the owner the provider and account name. The teammate cannot reconnect
or disconnect a shared account, but they can add their own account.
Team access cannot create that boundary. Use a provider account with
narrower access, or do not share the connection.
## Next steps
* [Give Chat the right context](/knowledge-base/chat/give-chat-the-right-context)
* [Browse connector and schedule guidance](/knowledge-base/connectors-automations)
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.
