Solution access & members
Each solution has its own members and roles — granted independently of platform access.
Access to a solution is managed per solution: each one has its own member list and its own roles, separate from your organization's projects. This page explains who can grant what, and how solution access relates to the rest of Compass.
Members and roles
Open a solution from the Solutions page to see and manage its members. Each member holds one role in that solution. Roles are defined by the solution itself — a solution ships with the roles that fit what it does — so the choices you see vary from one solution to the next.
Organization admins can manage every solution's members. A solution's own administrators can manage membership for that solution.
Granting access with an invite
When you invite someone to your organization, the invite can carry solution access with it: pick the solutions (and roles) they should have, and they land with everything in place — no second step after they accept. The same applies to project access. See Members & roles.
Solution access and platform access are separate
Compass keeps two kinds of access distinct, and neither implies the other:
- Solution access lets someone use the solution's application.
- Platform access (membership in the project behind the solution) lets someone open Compass and inspect the workflows, agents, deployments, executions, and traces that power it.
Most day-to-day users of a solution only need the first. Grant the second to the people who should see how the AI works and audit what it does — it's an explicit, non-escalating grant, so giving someone a solution never quietly gives them more.