Organizations
Everything in CortexHub lives inside an organisation. The organisation is your company's account and governance boundary: people, AI, connected tools, files, policies, billing, and history belong to one organisation and never cross into another.
Organisation
├── Billing, members, seats, usage, security settings
├── Groups and access rules (the tool gate)
├── Toolkit catalogue and inventory
├── Agents: Org Agents, member co-workers, and connected external clients
├── Approvals, sessions, audit, integrations
└── Per member: one co-worker, member connections, personal files and Brain
The organisation is the only customer-facing account and governance boundary. There is no separate workspace or sub-account layer.
What the organisation owns
- Billing, plan, and seats
- Members (the people who belong to the organisation)
- Organization-owned Org Agents and their agent groups
- Groups and the access rules that gate tools
- The toolkit catalogue and inventory
- Approvals, sessions, integrations, and the organisation audit trail
Owners and admins see the organisation-wide picture. Each member sees their own scoped version of the same views, covering only their own work. Your personal surfaces (co-worker, connections, files, Brain, approvals inbox) live under your own area within the organisation.
Roles
CortexHub has three roles. Each builds on the one below it.
| Role | Typical capabilities |
|---|---|
| Member | Chats with their own co-worker, uploads and manages their own personal files, uses the tools the organisation has made available, and tightens the rules for their own connected toolkits and personal files. A member can make their own guardrails stricter, never weaker. |
| Admin | Everything a member can do, plus organisation-wide management: creates and configures Org Agents, installs named Slack bots, invites and removes members, connects shared tools, decides which groups reach which tools, and sets the organisation guardrails. |
| Owner | Everything an admin can do, plus ownership-level control: grants and revokes the Admin role, and holds responsibility for billing and the organisation itself. |
An organisation always has at least one owner. The owner who creates the organisation can grant the owner role to others, and the last owner cannot be demoted.
Members do not manage organisation-wide guardrails, Org Agents, groups, or the toolkit inventory, and they can never loosen a rule the organisation set or re-enable a tool an admin disabled. What they can do is narrow the rules on the things they personally control. See Groups and access.
External members (gateway and API-only principals, such as a partner's named end users) hold the member role with no Cloud login. They reach the gateway and Platform API only, and each is isolated from every other.
Multiple organisations
A person can belong to many organisations and can own more than one. Use the organisation switcher to move between them. Organisations never share members, billing, or data, and switching changes everything you see to that organisation's context. You can be the owner of one organisation and a plain member of another at the same time.
Partners and embedded products
Partners use the same organisation model. A partner backend can provision organisations and members through the Platform API, then create programmatic Member Credentials or use the organisation gateway key for programmatic access. End customers interact through the partner's product or through CortexHub Cloud, depending on the integration.