Integrations
In Org space, open Settings -> Integrations to connect Slack, configure outbound approval destinations, and export observability data. Slack has two related uses: named Org Agent bots and operator approval delivery.
Slack for Org Agent bots
Connect the CortexHub app to your workspace once under the Slack section. Then enable named bots with the Slack App Configuration refresh token. CortexHub stores and rotates that organization-level credential so you do not paste a token for every agent.
After this one-time setup, open a hosted Org Agent under Org space -> Agents, select its Slack tab, and choose Add to Slack. Authorize the generated named app in Slack, then add the bot to the channels where it should work. Members can mention the bot by name, and the agent's group policies still govern every tool call.
SDK Org Agents run in your own runtime and do not have a hosted Slack bot. Use the Org Agents guide to choose the right runtime.
Approval Channels
Backoffice approvals go to the built-in Approvals inbox by default. Connect a delivery channel here so backoffice approval prompts can also reach your team where they work. You then choose which channel a given rule uses in Policies or a compliance profile (see Policies and approvals).
Slack
Connect your Slack workspace so backoffice approval rules can post an approval card to a channel you pick. Anyone who can see the message can approve or deny; the decision is attributed to their Slack identity, with no CortexHub account required. Invite the CortexHub bot to a channel, then pick that channel when you configure a backoffice rule.
Approval webhook
Deliver signed approval events to an HTTPS endpoint you control.
- Configure the endpoint URL; CortexHub generates a signing secret (shown once).
- Payloads carry the call context and a structured decision callback so your system can return its approve or deny verdict. Verify the signature on each request.
- Rotate secret issues a new signing secret; Send test validates delivery before you enable the webhook in production.
There is one approval webhook per org. Removing it, or disconnecting Slack, falls back to the built-in Approvals inbox for any rule that pointed at it.
Observability
Stream governed invocation spans to your own observability tooling. The Settings sub-tab configures destinations; Delivery history shows recent attempts.
- Spans are emitted in standard formats (OTLP JSON or OCSF) to any OTLP-compatible endpoint or OpenTelemetry collector you operate.
- Configure the endpoint and rotate its secret from this tab.
- Use the test delivery to validate the destination before relying on it.
These destinations are org-scoped, not configured per agent.