Members and roles
A team organization is shared by its members, and each member's role decides what they can do in it. Every request a person makes, from the console, astroctl, the API or Nova, is checked against their role in the organization it acts in. Members are a team organization feature: your default organization has only you.
Roles
- Viewer: Read the organization's clusters, applications, models, cost and findings, and use the API.
- Editor: Everything a viewer can, plus deploy, update, roll back and resync applications and models.
- Admin: Everything an editor can, plus clusters, add-ons, profiles, credentials, integrations, notifications and members.
- Owner: Everything an admin can, plus billing and deleting the organization. One per organization: the person who created it, until they transfer it.
Service accounts take the same Viewer, Editor and Admin roles, for automation. The console reads the roles, with their permissions, from the platform.
Before you start
- A team organization on the Enterprise plan, which includes members and the Admin role. The Developer plan has neither.
- To add, change or remove members: the organization's owner, with the account Admin role.
- The person's User ID. They copy it from Organization settings › Profile, or run
astroctl whoami.
In the console
-
Pick the team organization in the switcher, then select your name at the bottom of the sidebar, Organization settings, then Members. Team Members lists each member's User ID, Role, Status and Joined At.
Open zoom view -
Select Add Member. Enter their User ID and pick a Role; each role shows its permissions. Select Add Member.
Open zoom view -
To make someone the owner, open their row and select Make owner, then type their email to confirm. You stay on as an admin.
-
To remove someone, select the remove button on their row and confirm. The owner can't be removed ("The owner can't be removed. Transfer ownership first."), and nobody can remove themselves.
You should see
The member in Team Members with their role. They pick the organization in their switcher, or run astroctl org use <organization>, and work in it with that role straight away. A removed member loses access on their next request.
What a role change touches
- A new role applies on the person's next request, in the console,
astroctland their API keys alike. - Personal API keys act as their owner, so a key never does more than its owner's role allows.
- Every add, role change, transfer and removal is in the organization's audit log, under who made it.
Other ways in
- API: the organization members calls in the API reference.
With astroctl
Change a role from the command line; the console offers add, transfer and remove.
astroctl org add-user --user-id <user-id> --role Editor
astroctl org set-role --user-id <user-id> --role Admin
astroctl org transfer-owner --user-id <user-id>
astroctl org remove-user --org-id <org-id> --user-id <user-id>
They act in the active organization unless --org-id names another. Every flag: astroctl organization.
If it's refused
Next
- Service accounts, for automation with a role
- API keys
- Audit logs