Shared Connectors
Last updated: July 13, 2026
Shared connectors let one person connect an integration so teammates can use it without each signing in separately. Before this, every teammate had to connect tools like Jira or GitHub on their own — work stalled whenever someone hadn't yet authenticated. Now a workspace admin (or the person who set up the connection, via admin tools) can share it, and Rhythms automatically uses the right credentials in chat and through MCP calls.
Shared connectors are most useful when everyone on a team hits the same source — a shared GitHub org, a team Jira project, or any integration backed by one common account.
Sharing a connection
Sharing is managed from the admin Integrations area, not from My Connectors.
If you're a workspace admin:
Open Admin → Account → Integrations.
Find the integration and open its connections (or use the connections list on the Integrations page).
Choose Manage sharing on the connection you want to share.
Share with specific teammates, a team, or the entire workspace.
Once shared, teammates can use that connection without setting up their own OAuth flow. They won't see the underlying tokens or credentials — they simply gain access to run actions through the shared connection.
Note: Non-admin users who own a personal connection cannot share it from My Connectors today. Sharing is done through admin settings.
Using a shared connection
When a connection has been shared with you:
Open My Connectors.
Find the integration — it should appear as connected, often labeled Shared or Shared by [name].
If more than one connection exists for that integration (for example, your own plus a shared one), pick the one you want to use.
You only need to set an explicit default when multiple connections are available. If a shared connection is the only one you can access, Rhythms uses it automatically — you don't need to configure anything first.
After a default is set (or auto-selected), Rhythms uses those credentials for actions in chat and MCP calls. You don't choose the connection on every request.
Setting defaults per integration
You can set a default connection for each user-scoped integration in My Connectors. This matters when more than one connection exists for the same tool — for example, your own connection plus one shared by a teammate, or two different shared connections from different owners.
The default determines which credentials Rhythms uses for that integration in chat and MCP calls.
Role | What you can do |
|---|---|
Workspace admin | Connect integrations, share connections with teammates/teams/workspace, and manage all connections from Admin → Integrations |
Teammate | Use shared connections; set a default when multiple connections exist |
Everyone | Set a default per user-scoped integration in My Connectors |
Which integrations support this?
Shared connections apply to user-scoped integrations — tools like Linear, GitHub, Atlassian/Jira, Google Sheets, and similar MCP integrations where each person could otherwise connect their own account.
Some integrations work differently. Tenant-scoped integrations such as Slack and Teams messaging are set up once at the workspace level by an admin. They don't use the same per-user sharing flow described here.
For any integration to work, a workspace admin must also have enabled it for your organization. A shared connection on a disabled integration won't be usable until the admin turns it on.
FAQ
Who can share a connection?
Workspace admins, from Admin → Account → Integrations. They can share any connection in the workspace, including ones created by other users.
Do my teammates see my credentials?
No. Teammates use the shared connection to run actions against the connected source, but they never see tokens, passwords, or other underlying credentials.
What if I have both my own connection and a shared one for the same tool?
Set the one you want as your default in My Connectors. Rhythms uses your default for that integration in chat and MCP calls.
What if I only have access to a shared connection?
You don't need to do anything. Rhythms automatically uses the shared connection when it's the only one available to you.
Can I share with the whole workspace at once?
Yes. When managing sharing, you can grant access to the entire workspace, not just individual people or teams.
Which integrations is this useful for?
User-scoped integrations where the team hits the same source — shared GitHub orgs, team Jira projects, shared Linear workspaces, and similar shared accounts.
Does sharing a connection work in MCP calls?
Yes. Once Rhythms has resolved your connection (automatically or via your default), it uses the same credentials for both in-app chat and MCP calls.