On Belay

Slack bot

Ask Claude from Slack. Route approvals to the right people. The On Belay Slack bot brings your org's Claude context into the workspace your team already lives in — same roles, same scoped access, same guardrails.

Install the Slack bot

The bot is installed at the organization level, and only one workspace can be linked per org. You'll need Slack workspace admin permission to authorize it.

  1. In On Belay, go to Dashboard → Settings → General.
  2. Find the Slack section and click Add to Slack. You'll be sent to Slack's authorization page.
  3. Authorize the @onbelay bot for your workspace. Slack sends you back to On Belay with a confirmation.
  4. Invite the bot to any channel you want it to work in: /invite @onbelay.

Once installed, the Slack section shows your connected workspace name and a Reinstall or update permissions link. Use that link if you ever need to re-authorize — for example, after the bot's scopes change.

What the bot can do

  • Answer questions — Mention @onbelay in a channel and it responds using your org's context: your functional groups, Claude role, and the integrations your groups can reach.
  • DM support — Send a direct message to the bot for a private query. It loads your personal context the same way.
  • Read channel context — In channels it belongs to, the bot can read recent thread context so its answers stay relevant to the conversation.
  • Route approvals — When Claude proposes an action that needs sign-off, the bot posts an approval request so an owner can decide right in Slack.

Ask Claude from Slack

Mention @onbelay in any channel the bot has been invited to, or DM it directly. The bot identifies you by your Slack email — it must match the email on your On Belay account.

A few examples:

  • @onbelay what integrations does the Marketing group have access to?
  • @onbelay summarize our Shopify sales for this week
  • @onbelay what's our refund policy?

Behind the scenes the bot calls get_my_context and list_my_integrations for you, so it answers with your actual roles and scoped access — not a generic guess. See the MCP tool reference for what those tools return.

Approval workflows

When someone asks Claude to take an action that exceeds their group's permissions, Claude doesn't just do it. It raises an approval request instead.

  1. Claude identifies the action and the person it's acting on behalf of.
  2. The bot posts a structured request to your org owners.
  3. An owner clicks Approve or Deny right in Slack.
  4. Claude is notified of the decision and proceeds — or stops.

Approval requests go to your org's owners. They can act on them from the Slack message buttons or from Dashboard → Approvals. Both routes resolve the same request, so it doesn't matter which one an owner uses.

Troubleshooting

  • Bot doesn't respond to a mention — Confirm it's been invited to that channel with /invite @onbelay. The bot has to be a channel member to see mentions there.
  • Bot says it has no context for you — Your Slack email must match a user in your On Belay org. Check Dashboard → People to confirm the person has been invited and has accepted.
  • Approval requests aren't arriving — Approval routing identifies people by email, so the approver's Slack email must match their On Belay account email.
  • OAuth error during install — Make sure you're signed into the correct Slack workspace, and that you have workspace admin permission. Only workspace admins can authorize an org-level bot install.