Switch a surface's provider
How a surface comes to point at a connected tool instead of Crusible's own store, or back again, without touching the channel or its conversation.
What you'll have
Knowing what switching a surface's provider changes, in either direction, and why the channel and its conversation are untouched by it.
A surface is backed either by Crusible’s own store or by a connected tool, and either direction is the same action. A team that keeps its issues in Linear points Issues at Linear, and a team that would rather keep them beside the conversation points Issues back at Crusible. Neither is a step up from the other.
The control is a tool’s row in Integrations, which is workspace-level, so what switches is every surface that tool backs. Most tools back one: Linear backs Issues, Notion backs Docs, Sentry backs Dashboards. GitHub and GitLab each back two — Forge and Review — and switching either moves both.
Planned The Integrations pane carries no rows yet: it
opens on a blurred picture of the pane, the sentence
Connect GitHub, Linear, Slack and the rest, and keep their keys in one place.
and a disabled Coming soon control.
The rows
the switch is made on are the rows below, and none of them can be reached
today.
Select Settings, then, under Account, open Integrations.
Result The pane lists every tool the workspace can connect, with the connected ones reading “Connected” under the account they were authorised as. This one pane holds both directions of the switch, for every surface the tool backs.
Find the surface you are switching, by the tool that backs it now and the tool you want backing it next, and check whether either tool backs a second surface you did not mean to move.
Result Each row's one-line description names what it backs. A surface is backed by one provider at a time, so the row you are switching to is the row that holds the record afterwards.
Select Connect on the tool you are switching to, and authorise it — or select Disconnect on the tool you are leaving.
Result Switching to a connected tool: the row reads “Connected”, names the account, and the surface reads from the tool from then on. Switching back to Crusible: the row loses its “Connected” state, and the surface reads from Crusible's own store from then on.
Open a channel that has the surface enabled and select it in the surface switcher.
Result Every surface that tool backs changes, and nothing else does. The channel keeps its name, its members, its agents, its other surfaces and its whole conversation. Work already recorded in the tool you left stays in that tool, where it was recorded, under the account that recorded it — so a surface pointed back at Crusible reads Crusible's own store, which holds none of that work.
If this doesn't work
If Account does not appear in Settings, or Integrations is missing from it, your sign-in does not hold the permission that opens it: a pane you may not open is absent rather than shown and disabled, so ask whoever created the workspace to grant it. If the surface still shows the old data, the surface is reading a provider that is still connected — read the Integrations rows again and confirm the one you meant to leave no longer reads Connected. If a second surface changed too, that tool backs both of them, which is what the row does rather than a fault. If the surface shows nothing after a switch, the account you authorised may not be able to see the project or repository you expected on the tool’s side. If the channel itself looks different, something other than this switch changed it: the channel’s name, members, agents and conversation are set in the channel’s own settings. If a step still does not match what you see, Troubleshooting is written for that moment.
Each surface the tool backs then answers to the provider you chose, and the Integrations pane says which. What does not change is everything else: the channel, its members, its agents, its other surfaces, and the conversation that holds the work. The same steps run in the other direction the day the team wants them to.