Team owners can invite new members to a team, resend or revoke team invitations, change roles, and remove existing members. There is no limit to the number of members a team can have or the number of members who can have a given role.
The team page lists the team’s current membership:
All team members can see the membership table, including each user’s current Role (owner, biller, or member) and the Status of their invitation to the team (joined or pending). Team owners can additionally see each team member’s Sign-in method (email, email + 2FA, Google, or GitHub).
To invite more people to the team, click the Invite Members button. In the Invite team members window that opens, enter the email addresses or select the Gmail contacts of the people you want to invite, then click Invite team members. Invitations are sent via email.
When someone has not accepted their invitation to the team, the Status column lists them as pending. The … menu for pending team members has two options:
Resend email sends the invitation to join the team again.
Cancel invite revokes the invitation to join the team.
When someone has accepted their invitation to the team, the Status column lists them as joined. The … menu for joined team members has two options:
Change roles lets you change the member’s team role.
Remove member removes the member from the team, which removes their control panel and API access.
Team members can have one of three roles: owner, biller, or member. Roles determine a user’s level of access to a team’s shared resources, billing information, and settings.
|Role||Shared Resources||Billing Information||Team Settings|
|Owner||View and modify||View and modify||View and modify|
|Biller||View only||View and modify||No access|
|Member||View and modify||No access||No access|
When a team owner changes a teammate’s role to owner, the owner receives an email with a link to confirm the change. Once the owner confirms the change, the team member is sent an invitation to accept the new role.
Team owners can also require secure sign-in for all team members. This enforces everyone on the team to log in using a DigitalOcean account with two-factor authentication, Google OAuth, or GitHub OAuth.