Identity & access
Signing in
Section titled “Signing in”Sign-in is SSO through Google. Sessions are server-side and revocable — signing someone out actually signs them out, immediately, rather than waiting for a token to expire client-side.
Access to a team is granted, not inherited from org membership alone. A person can hold one of three roles on a given team:
| Role | Can do |
|---|---|
| Viewer | Read-only — watch runs, memory, and live output |
| Operator | Everything a viewer can, plus: chat with agents, run processes, approve or reject proposals, stop or dismiss a run, edit the schedule |
| Owner | Everything, including granting or revoking other people’s access to the team |
Roles are scoped per team, not per agent — an operator on team-atlas
has that access across every agent in that team, not a subset of them. If
you need one person to only touch one agent’s proposals, that’s not a
distinction Ravel’s grants make today; scope it by splitting the team
instead.
A team in an org you don’t have access to doesn’t just deny you — it doesn’t exist as far as you can tell. There’s no way to enumerate teams you can’t see.
Editor access is separate
Section titled “Editor access is separate”Git write access to a team’s repo is managed on GitHub, independently of a person’s viewer/operator/owner role on the platform. Someone can push code without being an operator, and vice versa — decide on your own repo permissions the same way you would for any other repo.