> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/connectivity/share-a-connector-with-your-team.md). # Share a connector with your team A shared connector lets one person sign in to an app once — GitHub, Linear, Google Sheets, Atlassian — and lets teammates use that connection without signing in themselves. A Rhythms Admin shares a connection from **Settings › Workspace › Connectors**, choosing specific people, teams or the whole workspace. Teammates then see it in **My connectors** marked "Shared by \[name]", and Rhythms uses it automatically in chat, in playbooks and in MCP calls. [Watch the video](https://assets.usepylon.com/9a10f540-a8ae-420e-b7b4-7e84b3bf4696%2F1788555879082-SharingConnectorsinPowerBI2026-07-14.mp4?Expires=253370764800\&Signature=O47HMM-q2p14mMHMNEHJFbyrR5Tzez8b5NRspjVPgRj5n19xEeSrsbQ-wFHY4BqL8P4tM2-F8vqFNTxA4OlWT25ST2DgKV1kcygh5LExP1Lz4mba8PJFQov1n8ivFy9r28TkKI35PG2nHAzBbcaBqhx9k53oh7QFyauFHGXrVsQlbBx~mAxu1JfjZF8FChAhUVitHXrZ1Dl5KOPHImMX9Jh6sEh3-cAMM56tXPqZWzXOE8nzi6eTMPllKJ9cATdzbCUJps~X1yXzshVS4ZDoCDS5hcDgvbtP-fxrBhtVJiaJKliBH36m9OmTZsF1atYdc0hMMNGKTvjR9ni6kOHYhA__\&Key-Pair-Id=K3NV4LZ47N8M46) ## When to share a connection Share a connection when everyone on a team works against the same source: a shared GitHub organisation, a team Jira project, a service account on a data warehouse, or a reporting spreadsheet one person maintains. Sharing also removes a common onboarding stall — a new team member can ask the agent about the team's work before they have connected anything themselves. Each person can still add a personal connection alongside the shared one and choose which to use. ## Share a connection (Rhythms Admins) 1. Open **Settings › Workspace › Connectors**. 2. Click the connector's row and open the **Connections** tab in the side panel. You can also click the number in the **Connections** column for a full-page list. 3. Find the connection you want to share, open its actions menu (three dots) and choose **Manage sharing**. 4. In the sharing dialog, set general access to **Everyone at \[your workspace]** to share with the whole workspace, or keep **Only invited users and teams** and add people by name or email, and teams by name. 5. Click **Save**. The connection's badge in the panel updates to **Workspace**, **Limited** (with a count of people and teams) or **Private**. People you share with can use the connection; they cannot change its sharing or remove it — only the connection's owner or a Rhythms Admin can do that. They also never see the underlying credentials. ### Connect and share in one step If nobody has connected the app yet, a Rhythms Admin can click **Connect** on the connector's row on the Connectors page, sign in with the account the team should use, and then share the new connection as above. ### Who can share Sharing is done from Settings and is available to Rhythms Admins. Members can connect their own accounts in My connectors but cannot share them from there today; ask a Rhythms Admin to share a connection for you. ## Use a connection that was shared with you 1. Open **My connectors** from the bottom-left corner of the sidebar. 2. A connector with a shared connection appears as connected with a **Shared** pill. Its card says **Shared by \[name]**, or **Shared with you** when the owner is not shown. 3. There is nothing to configure. When the shared connection is the only one you can use for that connector, Rhythms uses it automatically. Rhythms uses the shared connection wherever the agent runs for you: web chat, Slack and Microsoft Teams, playbooks, and AI tools connected through the Rhythms MCP server. ## Choose a default when you have more than one connection You may end up with several connections for the same connector — your own plus one shared with you, or two shared by different owners. In that case the connector's card in My connectors shows **Pick a connection**. Click the connection you want and it becomes your default for that connector; the card shows whose credentials are in use. You can change the default at any time. Defaults are per person and per connector, and apply only to user-scoped connectors. ## Which connectors can be shared Sharing applies to **user-scoped** connectors — nearly everything in the catalogue, including Linear, GitHub, Atlassian, Google Sheets, HubSpot, Salesforce and the Microsoft Teams Messaging and Microsoft Teams Meetings connectors, where each person would otherwise connect their own account. The exceptions are the **workspace-level bots**. The Slack bot and the Microsoft Teams bot that post notifications and answer questions are installed once for the whole workspace under **Settings › Workspace › Collaboration platforms**; everyone uses them without any sharing step, and they do not appear on the Connectors page. A shared connection only works while a Rhythms Admin has the connector enabled. If the connector is disabled, the shared connection is unusable until it is enabled again. See [Manage connectors for your workspace](/connectivity/manage-connectors-for-your-workspace.md). ## Stop sharing or remove a shared connection To narrow access, open **Manage sharing** again, switch general access back to **Only invited users and teams**, and remove people or teams. To remove the connection entirely, choose **Disconnect** from the same actions menu; the confirmation lists the auto-updates and playbooks that depend on it, because they stop working for everyone once the connection is gone. ## Frequently asked questions **Do my teammates see my credentials?** No. Teammates run actions through the shared connection, but tokens, passwords and other credentials are stored encrypted and are never shown to anyone. **I have both my own connection and a shared one for the same tool. Which does Rhythms use?** Whichever you picked under **Pick a connection** in My connectors. Until you pick, Rhythms uses the first one it can see, so set a default if it matters. **I only have access to a shared connection. Do I need to do anything?** No. Rhythms uses the shared connection automatically when it is the only one available to you. **Can I share with the whole workspace at once?** Yes. In the sharing dialog, set general access to **Everyone at \[your workspace]**. **Does sharing work in Claude, ChatGPT or Cursor through Rhythms MCP?** Yes. Rhythms resolves the connection for you — your default, or the only one available — and uses it whether the request came from the Rhythms app or from an AI tool connected through MCP. **What happens if the owner of a shared connection leaves?** If their access to the tool is revoked, the connection starts showing **Needs attention** for everyone who uses it. A Rhythms Admin should connect with another account, share that, and disconnect the old one. ## Related articles * [Manage connectors for your workspace](/connectivity/manage-connectors-for-your-workspace.md) * [Connect Rhythms to Your Favorite Collaboration Platforms](/connectivity/connect-rhythms-to-your-favorite-collaboration-platforms.md) * [Use Rhythms from Claude, ChatGPT or Cursor](/connectivity/use-rhythms-from-claude-chatgpt-or-cursor.md) * [How to Set Up Auto-Updates](/connectivity/connectors/set-up-automatic-updates-from-a-connector.md) * [Set up automatic updates from a connector](/connectivity/connectors/set-up-automatic-updates-from-a-connector.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.rhythms.ai/connectivity/share-a-connector-with-your-team.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.