Installing & managing extensions
Install, enable, disable, configure, scope and uninstall — and what each one means.
Everything lives at Org settings → Extensions. You need the connections-management permission, which usually means an Owner or Admin.
The manager
- 1Switch between Installed and All at the top.
- 2Click a row to expand it — you get What it adds, its Configuration, its Scope, and Uninstall.
- 3Install adds it to the workspace.
- 4Once installed, the Install button becomes an on/off switch — that's enable and disable.
- 5Save configuration applies the extension's own settings.
The four states, precisely
| Action | What happens |
|---|---|
| Install | The extension's surfaces appear and its jobs start. |
| Disable | Every surface disappears and every background job stops — on the server, not by hiding buttons. The install and all its data are kept. |
| Enable | Everything comes back exactly as you left it. |
| Uninstall | Removes the install and its scoping. Its data in other tables is deliberately kept. |
This is enforced everywhere the extension touches — pages, actions, background jobs and inbound webhooks. Disable Public Read-Only Boards, for instance, and its public URL returns "not found" immediately. That's why disabling is a safe, reversible way to switch something off while you decide.
Scoping to a division or team
An install is organization-wide by default. Scoping narrows it.
- 1Expand the extension and find Scope.
- 2Pick the divisions and teams that should have it. Select nothing to keep it available to the whole organization.
- 3The save button says which you're doing: Apply to whole organization or Save scope.
A scoped extension carries a Scoped pill in the list. Divisions themselves are created in Org settings → Structure.
When something refuses
Extension surfaces check four things in order, and tell you which one failed:
- "That extension isn't enabled for this workspace" — it isn't installed, or it's disabled.
- "You don't have permission to do that" — it's on, but your role doesn't allow this action.
- "The platform is in read-only mode" — a temporary platform-wide state; reads still work.
- Some extensions also need a plan — the message names the plan you'd need.
Publishing your own
You can submit an extension to the Marketplace. Submissions go through an approval step before they're listed, so the catalogue stays trustworthy.