Guides / Access and automation
Give a teammate access
To let someone else work in your project, you do not need their internal id. Create an invitation and send them the link. They get the role when they sign in with it.
Invite someone
- Open the console and pick the project.
- Choose Share access (the link icon in the activity bar).
- Answer the pages: the role, then how many days the link stays valid (1 to 30; 7 by default). The link is single-use.
- Copy the link and send it. It is shown once.
The person signs in, or creates an account, and the role is granted once. Until then you can revoke the invitation from Members.
Choose a role
Give the smallest role that covers the work.
| Role | Can |
|---|---|
viewer | read everything |
editor | read everything; create and change services (networks, DNS, DHCP, compute, storage, databases, queues, load balancing, diagrams) |
network-admin | everything in the network group |
network-user | read VPCs and manage accounts only |
owner | everything, and grant roles |
compute-admin, storage-admin, database-admin, queues-admin, edge-admin | manage that one service (storage-reader, database-viewer, queues-viewer and edge-viewer only read it). The editor role covers load balancing too. |
You can only grant a role you can grant yourself, so an invitation never gives more than its creator holds. The billing roles, billing-admin and billing-viewer, are granted on billing accounts, not on projects.
See and remove access
Members lists everyone with access to the current scope and the grant it comes through (this project, the owning account or a group). Pending invitations are listed there too. Remove a binding to revoke it. The last owner of a billing account cannot be removed, so add another owner first.
Review what changed
Audit log shows every successful change and every refusal in this scope, newest first, with the principal and the result. Reads and the contents of requests are never recorded. Owners can read the log of their projects. From the command line, ask for the refusals like this.
kubectl --context etorm get --raw '/clusters/acme-prod/etorm/v1/audit?outcome=denied&limit=20'
Invite with kubectl instead
An invitation is an ordinary object, so you can create it from a file.
apiVersion: iam.etorm.com/v1alpha1
kind: Invitation
metadata: {name: invite-bob}
spec:
roleRef: {name: editor}
maxUses: 1
expiresAt: "2026-12-01T00:00:00Z"
The create response carries the one-time token in status.token, and the link is https://console.etorm.com/invite/<token>. The token is never returned again, so copy it from that response.
Clean up
kubectl ... delete invitation invite-bob # an unused invitation kubectl ... delete rolebinding <name> # a grant that was used