Disconnecting integrations

The general pattern

Every integration has a Disconnect button on its detail page in Settings → Integrations. Clicking it:

1. Clears the stored OAuth token (or App install reference for GitHub).
2. Marks the integration as disconnected in your workspace.
3. Stops new sync from happening.

What it doesn't do:

• Doesn't always revoke our access on the third-party side. Some integrations require you to also revoke from the third-party's settings.
• Doesn't delete data we've already pulled. Backfilled customer data stays in your end user records, but stops updating.
• Doesn't unlink existing tickets that have been linked to issues, deals, or accounts.

Per-integration details

Stripe

Disconnect from Ochre clears the encrypted token. The Stripe panel disappears from conversations.

To revoke Ochre's access on Stripe's side, go to Stripe Dashboard → Settings → Connected accounts → Ochre → Revoke. Recommended if you're permanently disconnecting.

HubSpot

Disconnect from Ochre clears the encrypted OAuth token. HubSpot disconnect on our side does not unsubscribe webhooks on HubSpot's side. HubSpot will keep firing webhooks at our endpoint until an admin manually revokes Ochre from HubSpot → Settings → Integrations → Connected Apps.

The webhooks won't do anything (we ignore events from disconnected integrations), but they're noise. If you're permanently leaving, revoke on HubSpot's side too.

Linear

Disconnect clears the encrypted OAuth token. Existing ticket-to-issue links remain in the data; they show as "Linear (disconnected)" with no live status. Comments stop syncing.

To revoke on Linear's side, go to Linear → Settings → API → Authorized apps and revoke Ochre.

GitHub

GitHub uses an App install, not user OAuth, so there's a slightly different flow:

• Disconnect on Ochre's side. Marks the integration inactive but doesn't uninstall the GitHub App.
• Uninstall the GitHub App. Go to GitHub → Settings → Applications → Installed GitHub Apps → Ochre → Configure → Uninstall. This is the full revocation.

For a clean removal, do both.

Slack

Disconnecting removes the OAuth grant. The Ochre Slack app remains installed in your Slack workspace until removed from Slack → Apps. Slack Connect channels stop forwarding messages to Ochre.

If you reconnect later, previously linked channels reattach automatically. We don't lose your config.

Reconnecting

For most integrations, reconnecting is the same as the original setup: click connect, authorize, done. Configuration (which channels are watched, which routing rules use the data) is preserved across disconnect-reconnect cycles.

Backfilled data resumes updating from the moment of reconnect. We don't try to retroactively pull events from the disconnected period.

Permissions

Only Owners and Admins can connect or disconnect integrations. Agents see the integrations page but the connect and disconnect controls are hidden. The same role gate enforces token reads via the get_integration_token() server function, so agents can't pull a token even if they reach an internal endpoint. See Roles explained.

When you should disconnect

• The third party is no longer in use. You moved off Stripe, you don't use Linear anymore, etc.
• Compliance event. Security review requires you to revoke and rotate.
• Permission cleanup. A previous admin connected with their account; you want a service-principal install instead. Disconnect, reconnect with the right account.

What's next

• See Integrations overview.
• Read Integration permissions before reconnecting.