The Organization page
Click Organization in the sidebar. The page has five tabs:Members
Members lists everyone in the organization with their role.- Invite a teammate. An admin opens Organization, chooses Members, and invites them by email address, choosing the role they’ll have. The invitation is pending until they accept it from the email they receive; once they sign in, they’re a member and can use everything the role allows.
- Change a role or remove a member. For an admin, each member row has a menu to change their role or remove them from the organization. A member who is not an admin sees the list read-only.
A teammate who is not yet invited can’t get in. On the web, Clerk sends them to the choose-organization
step until an invitation arrives. In the CLI,
console setup stops with This account is not a member
of any organization — once they accept the invitation, they run console setup again.What needs an organization admin
Most of Console is open to every member: chat, projects, agents, detections, workflows, runs, findings, source-control connections, and vendor connectors. Managing the organization itself and a few other actions require the organization Admin role:
See connecting an app and Billing.
Organization API keys
The API keys tab holds keys that belong to the organization rather than to one person. The keys the CLI signs in with are personal — create those under Profile → API keys.Working in more than one organization
The web console works in one organization at a time — every page shows that organization’s projects, findings, and settings. There is no organization switcher in the web console today. The CLI can switch:/context <org> changes the organization a session works against. See
the CLI.
Next steps
Billing
Credits, payment method, auto-recharge, and usage.
Connect an app
The admin-only flow for Slack, Jira, Linear, Notion, Asana, and Google Docs.