Members & roles
Invite people to your organization, add them to projects, and control what they can do.
Access in Compass works at two levels: who belongs to your organization, and who can work in each project. You manage both from Settings.
Organization members
Settings → Organization → People lists everyone in the organization. Each person's row shows the role they hold in Compass, plus a chip for every project and solution they've been given access to — so one screen answers "what can this person reach?".
If you're an organization admin, you can also:
- Invite people — invite by email and choose, in the same dialog, the Compass role they'll land with and any project or solution access they should have from day one.
- Edit access — change someone's role and their project and solution access together.
- Remove someone — one action takes away their standing and every grant with it.
- Manage pending invitations — invitees appear on the roster right away, marked as invited, and can be revoked before they arrive.
Two guardrails: you can't change your own role or remove yourself, and the organization's last admin can't be removed.
Roles
Roles are Compass's own. The same three apply to the organization and to each project:
| Role | Can do |
|---|---|
| Admin | Everything a Developer can, plus manage people, settings, and spend limits, and delete projects. |
| Developer | Build and run — agents, workflows, deployments, and connections. Cannot manage people, settings, or spend limits. |
| Reviewer | Read-only. Can see everything, but not build, run, or spend. |
Someone can also be in the organization with no Compass role at all — they can use the Solutions they've been given access to, and nothing else.
Project members
Open Settings → Organization → Projects, pick a project, and use its People tab. You add people from your organization and give them one of the roles above.
Adding someone to a project draws from your organization's existing members; you invite people to the organization first (above), then grant them access to specific projects.
Admins span their organization
Administrators of the organization automatically have admin access to every project and solution in it, so they don't need to be added one by one — they show on each roster as holding that access through the organization. See Organizations.
How roles gate actions
Your role decides what you can do, not just what you can see. Everyday building — agents, workflows, deployments, and the connections they rely on — is open to Developers. Admin-only actions are the ones that change the shape of the workspace rather than the work in it:
- managing people and their access,
- editing project or organization settings,
- setting spend limits,
- and deleting a project.
Reviewers can see all of it and change none of it.