The Connections page at Projects → your project → Connections lists every third-party OAuth install attached to this project. Today that means Slack workspaces; Discord and Telegram will appear here as separate cards once they ship.
See Connections for the primitive itself — this page walks the dashboard surface.
The list
Each card shows:
- Workspace name — from the Slack team Nevo sees on install.
- Team id — opaque slack id, useful when cross-referencing Slack’s own admin UI.
- Status —
activewhen connected;disabledwhen Slack reports the token has been revoked externally. - Subscription count — how many channels (subscriptions) currently reference this connection.
- Granted scopes — small chips showing what permissions the install carries. Useful for spotting “why can’t I subscribe to channel messages?” when scopes like
channels:historyare absent. - Connected at — install timestamp.
Connecting a workspace
Click connect slack. You’re redirected to Slack’s consent screen. On approve you come back to this page with the new card visible.
Rules:
- A Slack workspace can be connected to one Nevo project globally. Trying to connect the same workspace to a second project produces a “workspace taken” error.
- Re-running the install from the same project acts as a reauthorize — it refreshes the bot token in place and unions any new scopes onto the existing card.
Disconnecting
The trash icon on each card starts a confirm flow. Nevo blocks disconnection while any channels still subscribe to the workspace — the error names the count. Remove those subscriptions first from the channels page, then return here.
On confirm:
- The Nevo bot is uninstalled from the Slack workspace via Slack’s
auth.revoke. - The connection card disappears.
- Past events + replies stay for audit (they don’t reference the connection, just the project).
If the Slack revoke fails (transient Slack outage), Nevo still removes the card locally so your intent to disconnect is honored — the app may show up as “Authorized” in Slack for a short while until Slack’s own reaper cleans it up.
When a connection goes disabled
Sometimes the Slack workspace admin revokes the Nevo app directly from Slack’s side. When Nevo next tries to use the token (for a reply, or a conversations.list call from the channel picker), the error surfaces and the connection status flips to disabled. The card shows a reauthorize button — click it to re-consent the bot and the status flips back to active. Channels on the connection stop receiving events until that reauthorize completes.
Plan availability
| Tier | Slack connections |
|---|---|
| Hobby | |
| Hacker | |
| Pro | ✅ |
| Scale | ✅ |
Related
- Connections concept — what the primitive is and why.
- Channels — subscribing to a slice of a connection’s events.
- Channels & endpoints dashboard — creating the subscriptions.