An organization is the account that owns everything in CodeCharter: rules, profiles, spec runs, the audit log, API keys, the subscription and its seats. When you register, you either join an existing organization or create your own; from then on, everything you do in the app happens inside one organization at a time.
This matters because most of the app is organization-scoped without saying so in the page name. Dashboard, Rules, Profiles, API keys, and Audit log all show data for one organization only: whichever one you currently have active. There is no view that mixes data from several organizations, and organization content is never visible to people outside it, not even a read-only public listing of its rules or profiles.
The active organization
If you belong to only one organization, that one is always active and you will not see any switching controls. If you belong to more than one, a switcher appears at the top of the sidebar showing the active organization's name. Open it to see every organization you are a member of and pick a different one.
Picking a different organization reloads the page. This is deliberate: it guarantees that everything on screen, from the dashboard tiles to the rule list, belongs to the organization you just selected, with nothing left over from the previous one. The active organization is remembered for your account and applies the next time you sign in, until you switch again.
Switching does not change what CI does. A CI pipeline authenticates with an API key or a license that already names its organization explicitly, so your personal active-organization choice in the browser has no effect on which organization a CI run reads from.
Organization-scoped vs. personal
A few pages under Account stay with you personally and look the same no matter which organization is active:
- Profile — your name, email, and password.
- GitHub connection — the GitHub identity linked to your account.
- Insights — your own coverage and usage dashboards across the repositories you work in.
Everything else you reach from the main navigation, including rules, profiles, spec runs, API keys, and the audit log, belongs to the active organization and changes when you switch it.
Membership and roles
Joining an organization happens by invitation or, if the organization has verified its email domain, by registering with a matching address and confirming the offer yourself. Every member holds exactly one role that governs what they can see and do, from read-only access up to full control including billing; see Roles and permissions for what each role covers.