Managed connector

Slack requests. Nexus control.

Turn explicit Slack requests into scoped Nexus jobs while approvals, source access, proof, policy, and spend remain governed in Orrery.

01

Request

Use /orrery run, plan, status, jobs, approve, deny, proof, or usage. Mentions and shortcuts only include text a user explicitly selects.

02

Bind

An organization admin maps approved Slack channels to a specific Nexus workspace and room. Identity linking uses a short-lived one-time code.

03

Review

Slack receives plans, approval cards, job state, failures, usage warnings, and redacted proof references. Open Nexus for source, diffs, and full evidence.

Data boundary

Selected context, not passive surveillance.

  • No broad channel-history ingestion by default.
  • No source code, raw diffs, credentials, full local paths, or private reasoning in Slack.
  • Writes, merges, deploys, downloads, external messages, and increased spend require policy approval.
  • Events are signature-verified, replay-protected, acknowledged quickly, and processed asynchronously.

Production availability depends on Slack app approval, configured OAuth credentials, organization entitlement, and current beta capacity.

Available with Orrery Business and Enterprise.

Business includes one Slack workspace and 10 bound channels. Enterprise supports an Enterprise Grid organization or up to five workspaces and 100 bound channels.

View organization plans