Projects and roles
How access, ownership and namespaces are organised, and what each role can actually do.
A project is the unit of tenancy. It bundles three things:
- Members, each with one role scoped to that project.
- Namespace bindings — “this project owns namespace
Xon clusterY”. - The workloads deployed into those namespaces.
A user with no project membership can sign in and see essentially nothing. That is the intended resting state, not a misconfiguration.
How you get a project
A personal project. Every activated user gets one automatically, named after them, with themselves as its admin. It exists so that a new account is immediately useful without anyone having to grant anything.
An invitation. A project admin adds you to theirs with a role.
Self-service, if the operator has enabled it. When on, any signed-in user can create a project and becomes its admin. It is off by default.
The three roles
Hierarchical — an admin can do everything a developer can, and a developer everything a viewer can.
| Viewer | Developer | Admin | |
|---|---|---|---|
| See the project and its workloads | ✓ | ✓ | ✓ |
| Deploy from the catalog | ✓ | ✓ | |
| Stop, resume and delete workloads | ✓ | ✓ | |
| Add and remove members | ✓ | ||
| Bind and unbind namespaces | ✓ |
Two things no project role grants
This is the part that surprises people, and it is deliberate.
Changing a workload’s shape — its image, replica count or resource limits — is reserved to platform administrators, whatever your project role. So is deploying a workload that does not come from a template.
The reason is that templates are the source of truth for what a workload costs. Image and scale changes move the bill, so they do not sit behind a role that every user already holds on their own personal project — that would be a boundary in name only. A developer runs what their admin shipped; if a different shape is needed, the template changes, or a platform administrator makes it.
Project admin is not platform admin
Two different things with confusingly similar names.
A project admin is scoped to one project: its members, its namespaces, its workloads.
A platform administrator is an account-level property. It grants cluster registration, the global audit log, and the workload changes described above. Being an admin of your own project does not make you one.