Org Agents
An Org Agent is an AI identity owned by your organization. It can run shared work for the organization, use the tools granted to its agent group, and be installed as a named Slack bot. Its activity is governed and audited as organization activity rather than as one member's private assistant.
Org Agents are different from the other agent types in CortexHub:
| Type | Runtime | Ownership | Slack surface | Credential path |
|---|---|---|---|---|
| Hosted Org Agent | CortexHub | Organization | Named bot that members can @mention | No runtime key required |
| SDK Org Agent | Your runtime | Organization | No hosted Slack bot | Org API key bound to the agent |
| Co-worker | CortexHub | One member | Member-private co-worker bot | Member connections |
| External client | Claude, Cursor, ChatGPT, or your runtime | Member or end user | No named bot by default | MCP OAuth or org gateway key |
Create an Org Agent
- Open Org space → Agents in CortexHub Cloud.
- Select Create Org Agent for a hosted agent, or Register Org Agent when the agent will run in your own SDK runtime.
- Give it a stable name and description. Use a name people will recognize in Slack.
- Enable only the capabilities it needs.
- Open the agent's Governance or Settings view and assign it to an agent group.
Agent groups are the tool gate. Publish the required toolkits to that group, review the read, write, and destructive policies, and add any stricter guardrails before the agent runs work.
Connect the tools it may use
Org Agents use organization-scoped access. Members do not connect a personal toolkit on behalf of an Org Agent. An admin should:
- Open Org space → Groups → Agent groups.
- Choose the agent group and publish the toolkits it needs.
- Configure the safety-profile policies and any per-tool rules.
- Test a representative read and write action while reviewing the decision, approval, and audit record.
Keep destructive actions denied or approval-gated until the workflow has been tested with real policy outcomes.
Add a hosted Org Agent to Slack
The Slack flow gives the agent its own named bot. Any permitted workspace member can mention it in a channel where the bot has been added.
One-time organization setup
- Open Org space → Settings → Integrations → Slack.
- Select Connect Slack and authorize the CortexHub app in the workspace.
- Enable named bots using the Slack App Configuration refresh token. Store this once at the organization level; do not paste a token for every agent.
Install the agent
- Open Org space → Agents and select the hosted Org Agent.
- Open its Slack tab and select Add to Slack.
- Authorize the generated Slack app when Slack opens.
- Add the bot to the channels where it should operate.
- Mention it with
@agent-nameand give it a small, reversible task first.
The agent runs as the organization. Each person's Slack thread remains separate, and every governed tool call still follows the agent group's policies. Slack installation does not grant tools by itself; group entitlement and policy still decide what the agent can do.
Approvals and audit
Configure back-office approval delivery separately under Settings → Integrations → Approval Channels. A Slack approval channel is where operators decide on a parked action. The named Org Agent bot is where members ask the agent to do work. They can use the same Slack workspace without being the same Slack app or channel.
Review Org space → Agents → [agent] → Sessions and the organization activity views after a test. Check the tool, policy decision, approval state, principal, and receipt before expanding access.
Hosted or SDK?
Choose a hosted Org Agent when CortexHub should run the agent and you want the named Slack bot. Choose an SDK Org Agent when your application owns the runtime and needs an organization-owned identity for MCP calls. SDK agents use an org API key bound to the agent; hosted agents do not need a runtime key.
Lifecycle
Block an agent for a temporary access stop. Archive it when it should stop running while preserving history. Restore an archived agent only after reviewing its group membership and policies. Purge is an owner-only, irreversible data-erasure operation.