Managing your organization
Adding team members to your org
Invitations, roles, and how membership gates access in ctx|.
Roles
Each member has exactly one role per organization:
| Role | Capabilities (summary) |
|---|---|
| owner | Full control including destructive org actions and ownership transfer. |
| admin | Manage members, repositories, and settings. |
| member | Work with repositories and conversations within the org. |
Roles are enforced across organization pages and MCP access.
Inviting by email
From the dashboard (Settings → Members), send an invitation. The invitee receives an email with an accept link.
- If the invitee already has an account, accepting attaches them to the org with the invited role.
- If they do not, they can sign up first; the invitation is applied when the email matches.
Switching organizations
Users in multiple organizations switch with the organization switcher. The URL updates so it is always clear which organization owns the current repository, conversation, connector, or graph context.
MCP and membership
MCP requests authenticate the user, then verify membership in the org implied
by orgSlug. Without membership, the call does not proceed - there is no
orgId knob inside tool schemas for agents to override.