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.
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.
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.
The owner's connected Google Drive account shows Team access as Not shared before anyone else can use it.
2
Turn on Team access
Turn on Team access. Confirm the state changes to Shared with team
and the member list appears.
After Team access is enabled, the owner sees Shared with team and can include or exclude each teammate independently.
3
Exclude members who should not use it
Leave the intended teammates on. Turn off access for anyone who should not
use this account. This does not affect other included teammates.
4
Set the permission boundary
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.
5
Enable the account as a teammate
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.
The teammate view identifies the shared company account, its owner and the enabled Use in my chats control in one contextual frame.
6
Run a read-only verification in Chat
Open a Chat and enable the provider under Connectors. If personal and
shared accounts coexist, name the company account in the request.
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.
A concrete read-only request returns the approved promise and audience note from the shared company brief without changing the source.
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.
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.
