> 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/manage-connectors-for-your-workspace.md). # Manage connectors for your workspace Connectors link Rhythms to the apps your teams already use — Linear, Google Sheets, Salesforce, HubSpot, Atlassian, Snowflake and roughly two hundred more — so Key Results and Initiatives update themselves and the Rhythms agent can read the right context. Every released connector is switched on when your workspace is created. As a Rhythms Admin you decide which connectors to keep, control which agent tools each connector exposes, and see who has connected what, all from **Settings › Workspace › Connectors**. ## How connectors work: admins enable, people connect Two different actions are involved, and it helps to keep them apart. * **Enabling a connector** is an admin decision about whether the connector is available in your workspace at all. Every released connector is enabled by default, so there is nothing to switch on and no master toggle to find. Your job as a Rhythms Admin is to switch *off* the connectors you do not want people to use. * **Connecting a connector** is what each person does with their own account under **My connectors**, in the bottom-left corner of the sidebar. Almost every connector is user-scoped: the person signs in to the app with their own credentials, and Rhythms can only read what that person can read. A Rhythms Admin can also connect once and share that connection with a team or the whole workspace — see [Share a connector with your team](/connectivity/share-a-connector-with-your-team.md). * **Workspace-level bots** are the exception. The Slack bot and the Microsoft Teams bot are installed once for the whole workspace under **Settings › Workspace › Collaboration platforms**, not on the Connectors page. See [Connect Rhythms to Your Favorite Collaboration Platforms](/connectivity/connect-rhythms-to-your-favorite-collaboration-platforms.md). ## Open the Connectors page 1. Click **Settings** in the sidebar. Only Rhythms Admins see Settings. 2. Under **Workspace**, choose **Connectors**. The Connectors page lists the whole catalogue, with a search box, category filters and a running total of connectors. Each row shows the connector's name, how many connections exist for it in your workspace, and a status: * **Enabled** — members can connect it. * **Needs attention** — enabled, but at least one connection has an error (usually an expired sign-in) and should be reconnected by its owner. * **Disabled** — you have switched it off for this workspace. * **Coming soon** — in the catalogue but not released yet. You can request it. Click any row to open a side panel with two tabs, **Tools** and **Connections**, described below. ## Disable a connector you do not want in the workspace 1. Find the connector with the **Search connectors** box. 2. Open the row's actions menu (the three dots at the right of the row) and choose **Disable**. 3. Read the confirmation and click **Disable**. Disabling a connector takes effect immediately for everyone in the workspace: * Nobody can create a new connection. In My connectors the connector shows an **Admin disabled** badge. * Existing connections stop working. Auto-updates on Key Results and Initiatives that use the connector stop syncing, and the Rhythms agent stops using the connector's tools in chat and in playbooks. * Goals keep their configuration and their last synced value; nothing is deleted. Tell the people who use the connector before you disable it — they lose the data in chats and summaries as well as in auto-updates. ## Re-enable a connector 1. On the Connectors page, open the row's actions menu and choose **Enable**. Rhythms Admins also see an **Enable** button on the connector's card in My connectors. 2. Some connectors show a short set-up note first. Read it and confirm. Existing connections come back without anyone having to sign in again. If a sign-in expired while the connector was disabled, the connector shows **Needs attention** and its owner reconnects from My connectors. ## Control which agent tools a connector exposes Most connectors are MCP servers, and each one offers a set of tools — some read data from the connected app, some change it. By default every tool is allowed. Tool controls let you narrow that per connector, and they apply to every connection of that connector, in chat and in playbooks. 1. Click the connector's row and open the **Tools** tab. The connector needs at least one working connection before its tools can be listed; until then the panel says "Connect this connector before configuring individual tool access." 2. Tools are grouped into **Read-only tools** (read data without changing the connected app) and **Write tools** (create, edit, delete or trigger changes). Tick or untick individual tools, or use **Allow all** and **Clear all**. Use **Search tools** for long lists. 3. Click **Save controls**. The panel header summarises the result — **All tools allowed**, **Selected tools allowed** or **No tools allowed** — with a count of read and write tools selected. A common pattern is to leave read tools on and switch off write tools for systems that should never be changed from Rhythms. ## See who has connected a connector The **Connections** tab of the side panel shows one card per connection: who owns it, whether it is healthy or has an error, and how it is shared — **Workspace** (everyone can use it), **Limited** with the number of people and teams, or **Private** (only the owner). Each card has an actions menu with **Manage sharing** and **Disconnect**. Disconnecting removes the connection for everyone who uses it, and auto-updates and playbooks that depend on it stop; the confirmation lists what is affected. Click the number in the **Connections** column for a full-page list of the same connections. ## Decide who can add custom connectors Anyone in the workspace can register their own MCP server from My connectors with **Add custom connector**. To limit this to admins, open the **Custom connector permissions** control at the top right of the Connectors page and choose **Admins Only** instead of **All Members**. Members then see the Add custom connector button greyed out with a note to contact their workspace admin. ## Request a connector that is not in the catalogue 1. Type the tool's name into **Search connectors**. 2. If the tool appears with a **Coming soon** status, click **Request**. If nothing matches, enter the name in the box under "Can't find what you're looking for?" and click **Request**. You will see "Request submitted. We'll notify you when it's available." Rhythms keeps one request per tool per workspace, so if a colleague already asked you will see **Already requested** instead. Members can request connectors from My connectors in the same way. ## Deprecated connectors Occasionally a connector is replaced by a better one. A deprecated connector is not available for new connections and cannot be re-enabled, but existing connections keep working until their owners remove them. Today **Jira** is deprecated in favour of **Atlassian**, which covers both Jira and Confluence through Atlassian's own MCP server. Ask Jira users to connect Atlassian instead. ## Frequently asked questions **Who can manage connectors?** Only Rhythms Admins can enable, disable, share, disconnect or set tool controls on connectors. Members connect their own accounts, request connectors and, unless you restrict it, add custom connectors. **Do I need to turn connectors on for my team?** No. Every released connector is enabled when the workspace is created. Only disable the ones you do not want. **Can I restrict a connector to certain teams?** Not at the connector level — an enabled connector is available to every member. If one team should use a specific account, connect it once and share that connection with the team; other members can still connect their own accounts. Tool controls limit what any connection of the connector can do. **If I disable a connector, do people lose their sign-ins?** No. Connections are kept but inactive. Re-enabling the connector restores them; only sign-ins that expired in the meantime need reconnecting. **Can I connect a connector on behalf of my team?** Not with their credentials — each person signs in themselves. You can connect with your own account using **Connect** on the Connectors page or in My connectors, then share that connection with a team or the whole workspace. **Why does a connector show Needs attention?** At least one connection has an error, most often an expired or revoked sign-in. Its owner should open My connectors and choose **Reconnect**. **Do I have to handle API keys or passwords?** Not for OAuth connectors, which are the majority — each person signs in through the tool's own login page. A few connectors take a personal access token that the person pastes in; Rhythms stores it encrypted and never shows it again. **Where do Slack and Microsoft Teams live?** The Slack and Teams bots that post notifications and answer questions are workspace-level and are installed under **Settings › Workspace › Collaboration platforms**. The connectors named Slack and Microsoft Teams Messaging on the Connectors page are personal connections for reading messages and meetings. ## Related articles * [Share a connector with your team](/connectivity/share-a-connector-with-your-team.md) * [How to Set Up Auto-Updates](/connectivity/connectors/set-up-automatic-updates-from-a-connector.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) * [Set up automatic updates from a connector](/connectivity/connectors/set-up-automatic-updates-from-a-connector.md) * [Rhythms OKR Roles and Permissions](/workspace-settings-and-administration/team-users-and-access/okr-roles-and-permissions.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/manage-connectors-for-your-workspace.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.