Team and roles

#Roles

Everyone in an organization holds one role. They are fixed (there is no policy editor), so give each person the narrowest one that still lets them work.

• Owner: full control. Whoever creates the organization is its first Owner.
• Admin: recommended for engineers: builds and destroys infrastructure, but cannot touch payment methods.
• Viewer: for contractors and anyone who needs to look, not change.

A Billing role, for finance staff who need invoices but never a server, is shown in the console but cannot be given yet.

There is no charge per member.

#Invite someone

1. Go to Team and press Invite member.
2. Enter their Email.
3. Choose a Role. What each role can do compares them side by side.
4. Press Send invite.

They get one email with a link. The invite shows on Team as pending, with when it was sent and when it expires. If it has not arrived, press Resend on its row.

Accepting an invite covers what they see.

#The team list

Team lists every member with their role, whether they have two-factor on, when they were last active and when they joined. Filter it by role, two-factor or status.

Two-factor matters most for Owners and Admins, who can destroy machines and move money. The page tells you how many people can sign in without it. Ask them to turn it on.

#What a member leaves behind

Removing a member does not delete what they built. Their virtual machines, keys and volumes stay with the organization.

Their SSH keys stay on every machine that already has them, though. Rotate those yourself when someone leaves.

#Changing a role or removing a member

Open the member from Team. Owners can change anyone's role and remove anyone; Admins can do both for Viewers. Neither applies to yourself.

Change role lists every role with what it would let the member do. A role you can't grant is listed but greyed out. Making someone an Owner or Admin warns you first, more strongly when the member has no two-factor, and the change takes effect at once, without the member signing out and in.

Remove ends the member's access at once and signs them out. Nothing they built is deleted.

#Your organization

Organization, in the account menu, shows the organization's name, its region, when it was created, how many members and machines it has, and its balance.

Owners can rename it there, and set its Security policy: Require two-factor for everyone, or for Owners and Admins only. The page says whether the platform enforces the policy yet; once it does, anyone not enrolled gets an email and 7 days to turn on two-factor before they're locked out. Every Owner is always emailed when a machine or volume is destroyed.

#Delete the organization

Owners see a Delete organization card listing what deleting would take: every machine, volume, network, security group, snapshot and SSH key, every member's access, and any credit left, which is forfeited. Press Delete organization and type its name to confirm. It can't be undone.