Organizations and access
How membership, source scope, and agent access fit together in ctx|.
An organization is the access boundary for repositories, connections, conversations, graph context, and MCP. People can belong to more than one organization and switch between them in the product.
Organization context
- Each organization has a name and a unique URL slug.
- The organization switcher changes the active product context.
- Repository, Chat, graph, and connector pages always operate inside the organization shown in the URL.
- MCP includes the organization slug in its server URL and verifies that the signed-in user is a member.
Repositories, not projects
The product surface centers on repositories under an organization. Treat each registered repo (or monorepo) as the unit of code connection and ingestion. There is no separate project container between an organization and its repository inventory.
Access follows both membership and source scope
Organization membership gives a user access to the ctx| organization. It does not widen the upstream source scope:
- GitHub App repository selection controls which code ctx| can read.
- Connector scope controls which Linear, Notion, or Confluence content is mirrored.
- Repository permissions control who can read connector-generated Git content.
- Slack captures require the bot to be present in the channel.
Use roles to control administration inside ctx|, and keep provider permissions and context-repository audiences deliberately narrow.