A shared workspace has a Connectors list in its settings. It lists every connector Bluedeer supports, each once, as Allowed or Not allowed:
- the built-in services, such as Gmail, Google Calendar, Google Drive, Google Docs, Google Sheets and Slack;
- every popular connector you can add with one click, such as Linear, Notion, Airtable or Atlassian;
- the workspace's custom connectors: connectors at a server address that isn't in the list. Only the owner and admins put an address on this list.
Members can connect only what is allowed, and each person connects their own account. Your Personal workspace is different: its built-in services and all connectors are allowed from the start, as far as your plan includes them (see Plans below), you can add any address, and there is no list to change.
A new shared workspace starts with everything not allowed. This is deliberate: nothing from outside reaches the workspace until the owner or an admin chooses it.
Every service belongs to one category: Communication, Email & calendar, Files & documents, Project management, Productivity, CRM & sales, Support & feedback, Marketing, Finance & payments, Analytics & data, Developer tools, Design & media, HR & people, AI & automation, Legal & security, Research & learning, and Travel & lifestyle. The list is grouped by category, each with a heading that says how many it holds.
- A search box at the top finds a connector by its name, by what it does, or by its category's name ("finance", "design"). If nothing matches, the list says so.
- Under the search box, Categories narrows the list. On the web, select it and tick one or more categories to see the connectors of any of them; the categories you ticked show as small labels beside the button, and Clear shows every category again. On the phone, a row of category buttons scrolls sideways above the list and narrows it to one category.
- Above the list, you can see how many are allowed, for example "1 of 536 allowed". While you search or choose categories, it also says how many were found.
Open the Connectors list
On the web:
- Select Workspace in the sidebar, then Settings.
- Open the Connectors tab.
On the phone:
- On the home screen, tap the button at the top right, then Manage workspace.
- Open General.
- In the Connectors section, tap Connectors.
Who can change it
- The owner can always change it.
- An admin needs a paid seat in the workspace. Without one, an admin can see the list but not change it.
- Members see only what is allowed, with no switches. On the web the list says "The workspace's owner or an admin chooses which connectors this workspace allows." A member who wants another custom connector asks for it (see Ask for a custom connector).
What the list shows
Each connector shows its name, what it lets Bluedeer do, and its status. Built-in services show Built-in next to their name and come first in their category.
- For the owner and admins: how many people use it, for example "Allowed · 2 people connected" for a built-in service, "Allowed · 1 person added it" for a connector, or "Allowed · nobody added it yet". You only see a number. You never see who it is or which account they used.
- For everyone: whether your own account is connected, for example "Allowed · your account is connected" or "Allowed · add it in Customization → Connectors".
Allow a connector
The owner or an admin turns on the switch next to it. Allowing it doesn't connect anyone. Each person then connects their own account from Customization → Connectors, or from a card in a chat. An allowed popular connector appears in each person's popular connectors; one that isn't allowed isn't offered there, and the assistant doesn't suggest it. See How do I connect a service from a card in chat?
To see one company's apps together, such as Google's, the owner or an admin chooses it under Brand in the filters above the list. The apps usually connected together come first, and each is allowed with its own switch.
Slack needs one extra step. After it is allowed, the owner or an admin connects first, from Connectors or a chat, and that chooses which Slack workspace this workspace uses. Until then, members see that they are waiting for an admin to connect the Slack workspace.
Add a custom connector to the list
Under Custom connectors, the owner or an admin enters a name and the connector's server address (an https address on the public internet) and selects Allow address. Bluedeer first checks that a server answers at that address, either by listing its tools or by asking for a sign-in. If it doesn't answer, nothing is added and you see why, for example "Could not connect to the connector. The server could not be reached." Once it is on the list, members can add it in Customization → Connectors, where it shows under Allowed in this workspace with Connect, and sign in with their own account.
An address that belongs to a popular connector can't be added here: allow that connector with its own switch instead.
An owner or admin can also add a custom connector for themselves in Customization → Connectors. Its address goes on the workspace's list only once their own connection works:
- For a server that needs no sign-in, or one you give a key to, Bluedeer tests the connection first. The address is allowed when the test succeeds. If the test fails, nothing is added, neither your connector nor the address, and you see the reason.
- For a server you sign in to, the address is allowed when you finish signing in and the server answers. Until then, only your own connector waits for your sign-in. Members can't add it yet.
Ask for a custom connector
A member who adds a connector at an address the workspace doesn't allow is asked first: "Send for approval?" The request goes to the owner and admins with the name and address the member entered. The member's own sign-in details are not sent. Until it is answered, the member sees it as Waiting for approval in Customization → Connectors.
Each owner and admin gets an Inbox item under Needs your attention. To review requests, open Customization → Connectors and select Requests (the button shows how many are waiting). Each request shows:
- who asked;
- the server's address and the name they gave it;
- the tools it offers, when the server lists them without a sign-in (described by the server itself);
- when they asked.
Select Accept or Decline, with an optional reason the member reads.
- Accept first checks that the server still answers. If it doesn't, the request keeps waiting and you see why, so you can try again later or decline it. Otherwise the address goes on the workspace's list as allowed. When the server needs no sign-in, it is also connected for the member who asked; otherwise they connect it with their own account. The member gets a notice.
- Decline leaves it not allowed. The member gets a notice with your reason, if you gave one, and can ask again later.
Both answers are recorded in the workspace's Activity, and the other reviewers' Inbox items close.
Popular connectors are not requested this way: a member asks the owner or an admin to allow them.
Stop allowing a connector
Stopping a connector works the same way for every kind: a built-in service, a popular connector and a custom connector.
- Turn off the switch next to it.
- Bluedeer asks you to confirm. The question names the connector and says how many people will be signed out, for example "2 people will be signed out of Linear and get a notice." You never see who they are. If someone connects while the question is open, Bluedeer asks again with the new number.
- Confirm with Stop allowing.
Then, in this workspace:
- Everyone is signed out of it. Each person's sign-in to it is deleted, together with its stored keys and tokens, and Bluedeer ends the sign-in at the service when the service supports that. For Google services, a person who still uses another Google service in Bluedeer (for example Gmail in their Personal workspace) stays signed in to Google for that one.
- Its tools stop at once, in chats, scheduled tasks and live pages.
- Each person who was signed in gets a notice: "An owner or admin stopped allowing it in this workspace, so you were signed out of it." The owner or admin who stopped it doesn't get one.
- Activity records it, with who did it and how many people were signed out.
Allowing it again doesn't bring anything back. Nobody is signed in again: each person connects their own account again.
Remove takes a custom connector off the list. It works like stopping it, with the same confirmation, and everyone is signed out of it.
Connections in other workspaces are never touched.
How it fits with people's own connections
- Allowing only allows. It never signs anyone in. Each person connects their own account, and only they can use it. Other people in the workspace, the owner and admins included, can't use someone else's account.
- A person can disconnect at any time. Disconnecting removes only their own sign-in. See How do I disconnect a service?
- Bluedeer's own tools are not on this list. Memory and web search are part of Bluedeer itself, so an owner or admin cannot switch them off here.
- Each tool's own rules still apply. Whether a tool asks first, a project's own choice of connectors, and Enterprise rules work as before.
Activity
Every change is in the workspace's Activity: allowing or stopping a connector (with how many people were signed out), adding or removing a custom connector, and each request asked, accepted or declined, with who did it. A custom connector is named there, never its address.
Plans
Every seat in a shared workspace is Pro or Max, and a connector on the list can be used once it is allowed, if the seat's plan includes connectors (Slack: if it includes Slack). Connectors are included on paid plans by default; your plan page shows what your plan includes. Slack is included on paid plans by default; your plan page shows what your plan includes. See Use Slack