Skip to content

Roles and permissions#

Astralyx has two layers of roles. An organisation role says what a person may do with the organisation itself — its people, workspaces, clusters, machines and settings. A workspace role says what they may do inside one workspace — with its runs, models, agents, notebooks and the rest, in every product. This page lists what each role allows, from the rules Astralyx enforces, and how to choose. To give roles, see Members and invitations and Workspaces.

How the two layers combine#

flowchart LR
  P[Person] -->|"organisation role:<br/>owner · admin · member"| O[Organisation]
  P -->|"workspace role:<br/>admin · editor · viewer · auditor"| W[Workspace]
  O --> W
  W -->|its access on each cluster| C[Cluster]
  • Organisation owners and admins are admin in every workspace of the organisation, without being added to it.
  • Organisation members see only the workspaces they were added to, with the role they were given there. A member in no workspace sees the organisation, its members and its clusters, and nothing else.
  • A workspace role holds on every cluster the workspace has access to, and for every product.

Whatever someone does in a workspace — from the console, astra, the API or an MCP client — is done as them, with their workspace role, and confined to that workspace. Nothing a person does in one workspace can read or change another workspace's work, even on the same machines.

Outsiders see nothing

Someone who is not a member of an organisation gets 404 ORG_NOT_FOUND for it, not 403: its existence is not revealed. Someone outside a workspace gets 404 WORKSPACE_NOT_FOUND.

Organisation roles#

Capability owner admin member
See the organisation, its members, its clusters, their prices and reservations ✓ ✓ ✓
See the organisation's guardrails and marketplace settings ✓ ✓ ✓
See usage and cost of the workspaces they belong to ✓ ✓ ✓
See usage and cost of every workspace, and of work outside workspaces on dedicated clusters ✓ ✓
Rename the organisation ✓ ✓
Invite people as admin or member; list and revoke invitations ✓ ✓
Change a member's role between admin and member; remove a non-owner ✓ ✓
Grant or revoke owner; remove an owner ✓
Create and delete workspaces ✓ ✓
Give a workspace access to a cluster, change its terms (quota, pools, priority, host access), remove the access ✓ ✓
Use Astraeus Cloud; rename or remove a cluster from the organisation ✓ ✓
See every machine of a cluster and its events ✓ ✓
Add machines; update, cordon, move between pools and remove them; choose data locations; clear GPU faults ✓ ✓
Reserve machines ✓ ✓
Set a dedicated cluster's prices ✓ ✓
Configure single sign-on ✓ ✓
Read the audit log ✓ ✓
Manage alerts and event streams ✓ ✓
Write the organisation's agent guardrails; marketplace approval ✓ ✓
Act as admin in every workspace ✓ ✓
Delete the organisation (only when it has no clusters) ✓
Leave the organisation (except the last owner) ✓ ✓ ✓

Refusals: 403 ORG_ADMIN_REQUIRED, 403 ORG_OWNER_REQUIRED, 409 LAST_OWNER.

Workspace roles#

Role In the console Meant for
viewer sees everything, changes nothing People who follow the work: managers, on-call, reviewers.
editor runs and changes work The team's engineers and researchers.
admin also manages people The team's lead.
auditor reads the agents' governance record, makes evidence packs Compliance and security reviewers who must not see workloads or data.

What each workspace role may do#

✓ allowed · read: see, never change · — refused.

Capability viewer editor admin auditor
All products
See the workspace, its people, its clusters and their terms ✓ ✓ ✓ ✓
See the workspace's events and its usage ✓ ✓ ✓ ✓
Remove themselves from the workspace ✓ ✓ ✓ ✓
Add, change and remove the workspace's people; rename it — — ✓ —
Set how long its events are kept — — ✓ —
Astraeus
Runs, workers and their logs, schedules, replica groups, endpoints read ✓ ✓ —
Stop or requeue a worker; reach a worker's or an endpoint's port through Astralyx — ✓ ✓ —
Drives, data sources and their catalog read ✓ ✓ —
Credentials (their references; values never reach Astralyx) read ✓ ✓ —
Machines in the workspace's pools, their GPUs and metrics read read read —
Use run templates / save and delete them use ✓ ✓ use
Eos
Models, deployments, API keys, shares with other workspaces read ✓ ✓ —
Turn the hosted inference gateway on or off — — ✓ —
Anemoi
Agents, flows, evaluations, connections read ✓ ✓ —
Decide approvals (when the approval names them, their role, or editors) — ✓ ✓ —
Guardrails, budgets and retention policies of the workspace read read ✓ read
The governance record: agents and versions, runs, costs, receipts, traffic, quality, approvals, flows, eval runs read read read read
Evidence packs: create, download, delete — — ✓ ✓
Hesperus
Notebooks and runtimes read ✓ ✓ —

The auditor sees the governance record without the workloads: no run, log, worker, drive, credential or notebook, and no approval's details (the held call's arguments).

Refusals: 403 WORKSPACE_ADMIN_REQUIRED, 403 WORKSPACE_EDITOR_REQUIRED on workspace settings; 403 RBAC_FORBIDDEN on work inside the workspace, for example role viewer may not create jobs in ws-3f9a1c07b2e4.

What no workspace role can do#

Whatever the role, a workspace cannot:

  • see or change another workspace's work: on a shared machine, other workspaces' work appears only as taken capacity (its GPUs and size, never its name or owner);
  • change machines, reservations or the workspace's own terms (quota, pools, priority, host access) — those are organisation decisions;
  • use a host path or privileged work the organisation did not grant it (403 HOST_ACCESS_FORBIDDEN);
  • ask for a priority above its maximum (403 PRIORITY_NOT_ALLOWED);
  • change or remove one of the organisation's agent guardrails.

Machines have no role#

Machines are not people. A machine's credential lets it act only for itself: receive the work placed on it, report on itself and its own workers, and answer requests addressed to it. It cannot read or change anything in a workspace. See Security model.

Choose roles#

  • Give each person the narrowest role that lets them work: viewer for people who only follow, editor for people who run work.
  • Keep organisation admins few: each is an admin of every workspace and can grant host access, which is root on the machines.
  • Keep two owners, so the organisation never depends on one person.
  • Give compliance reviewers auditor, not viewer: a viewer reads logs and data catalogs; an auditor does not.
  • Automation acts as the person whose token it uses. Create a dedicated account for CI with the narrowest role; see API tokens and automation.