DigitalOcean team roles: what each member can actually do

On a DigitalOcean team, the Member role has full access to every shared resource, deletes included. For day-to-day work, give people Modifier, and use a custom role or a second team when you need a tighter line than the predefined roles offer.

On a team of two or three, roles get set once, on the day someone is invited, and are never looked at again. The Member role is broad, so that is usually how a contractor ends up with almost the same power over production as the person who set it up.

The six predefined roles

DigitalOcean's predefined roles page says teams come with six: owner, biller, billing viewer, member, modifier and resource viewer. Here is how it divides access across shared resources, billing and team settings.

Predefined DigitalOcean team roles, as documented on 1 November 2026
RoleShared resourcesBillingTeam settings
OwnerFull accessFull accessFull access
BillerNo accessFull accessNo access
Billing viewerNo accessLimited, read onlyNo access
MemberFull accessNo accessRead only
ModifierFull access except deleteNo accessRead only
Resource viewerRead onlyNo accessRead only

The modifier, resource viewer and billing viewer roles are newer. DigitalOcean's release notes record them in August 2024.

Member is wider than the name suggests

Read the Member row again. Shared resources include all DigitalOcean resources, so a Member can create and delete Droplets, databases and volumes, and can use team SSH keys. That includes the Cloud Firewalls in front of your Droplets, so a Member can loosen them as easily as create them. They cannot see billing and they cannot change team settings, and only owners can invite people, change roles or remove members.

Members can also create personal access tokens. The API tokens article covers why that matters, and the rule here is the one from DigitalOcean's token page: the permissions of a team role control the scopes available to your tokens. A token can never reach further than its owner.

So the question to ask when you invite someone is whether they need to delete things. A developer who deploys and debugs rarely does. Modifier gives them full access to everything except deletion, and that single missing action turns a mistyped command into a recoverable event, not a lost database.

Custom roles for a tighter line

If six roles are not enough, custom roles let you pick the permissions yourself. DigitalOcean's release notes show them in private preview in March 2025 and generally available in June 2025. They are free, there is no stated limit on how many you create, and they are managed in the control panel. The permission groups include tokens, Spaces access keys, team membership and Projects, so you can build a role that deploys applications and cannot touch keys or tokens.

Note that custom roles live in one team. We found no way to copy a custom role from one team to another.

What roles cannot do

Roles apply to the team as a whole. The predefined roles table has columns for shared resources, billing and team settings, and nothing in it limits a role to one Project. The custom role permissions that mention Projects control actions on projects, such as creating or assigning resources, not access to a single project's contents. DigitalOcean describes Projects as a way to organise resources into groups.

That leaves one real workaround for separating environments. Teams are available at no cost, so keep production in its own team with a short list of people, and let developers work in a staging team where a broader role is fine. It costs nothing to set up and is the only boundary the documentation gives you.

Secure sign-in and SSO

Owners can require secure sign-in for every member, under Settings, Team, Secure sign-in. Only people who sign in with Google, GitHub or a DigitalOcean account with two-factor authentication can then reach the team. Read the fine print: the team limits page says Google and GitHub sign-ins are accepted, but DigitalOcean does not detect or enforce two-factor authentication on them. The setting is useful, though it is not the same as requiring 2FA from everyone.

For teams that run an identity provider, DigitalOcean supports single sign-on over OIDC, with Okta, Microsoft Entra ID, Auth0, authentik, JumpCloud and Keycloak documented. It offers a setting to require sign-in through SSO only, and an optional claim that maps people to team roles. Two details: SAML is not mentioned, and a default SSO role cannot be Owner, so you promote owners in the control panel after they join. SSO was released in August 2025.

What removing someone leaves behind

Taking a person off the team is the step most often treated as the end of the job. DigitalOcean's documentation is careful about it. The manage-membership page says removing a member removes their control panel and API access. The team limits page then adds the caveat that matters: it does not revoke their access to Droplets through SSH keys or other credentials, so you must revoke credentials on multi-user Droplets independently.

In practice that is a checklist. Remove their key from authorized_keys on every Droplet where it was installed. Rotate any Spaces keys they knew, and any token that was shared with them. What the documentation does not state is what happens to the removed member's own personal access tokens, or to SSH keys they uploaded to the team, so treat both as unknown and check.

Owners, and the last one out

A team can have more than one owner. When an owner changes someone else's role to owner, the original owner confirms by email and the new owner then accepts an invitation. We found no documented maximum and no explicit recommendation to keep two, but the reason to have a second is in the documentation: if you are the last owner on a team and you leave, the team is deleted and its payment method is charged the final balance.

Seeing what people did

The Security History page records actions such as creating or deleting resources and API tokens, with the user, the originating IP address and the time. Three limits to know. No retention period is stated, and DigitalOcean says to open a support ticket for older data. No export is documented. And creating and deleting tokens is recorded, while their use is not documented as logged.

It is also worth knowing what is missing from the tooling. The team limits page says the control panel is the only way to manage teams, and that the API and doctl do not support teams. There is no command that lists your members, so the audit is a visit to the control panel. We found no documented invitation expiry either, so a stale invitation is a thing to cancel by hand.

A review you can do in ten minutes

  1. Open the member list and look at every role. Anyone with Member or Owner who does not need delete rights should be a Modifier.
  2. Confirm there are at least two owners you actually know.
  3. Switch on secure sign-in, understanding its limit for Google and GitHub logins.
  4. Open Security History and look for token creations you do not recognise.
  5. Move production into its own team if it shares one with experiments.

FAQ

What is the difference between Member and Modifier on a DigitalOcean team?

Both have no billing access and read-only team settings. Member has full access to shared resources. Modifier has full access except delete, which makes it the better everyday role for developers.

Does removing a member revoke their access to my Droplets?

It removes their control panel and API access. DigitalOcean states it does not revoke access that goes through SSH keys or other credentials, so remove those from each Droplet yourself.

Can I limit a role to a single DigitalOcean Project?

We found no documented way. Roles apply to the whole team, so a separate team for production is the available boundary.

Does secure sign-in force two-factor authentication?

Not fully. It requires Google, GitHub or a DigitalOcean account with 2FA, but DigitalOcean says it does not detect or enforce 2FA on Google or GitHub logins.

Secorvia connects DigitalOcean with a read-scope token you create under the team you choose; the connection guide and the DigitalOcean page have the detail. Your team role caps the token scopes available to you.

Keep reading
DigitalOcean · 5 min read

DigitalOcean API tokens: what a leaked one can reach

DigitalOcean · 6 min read

DigitalOcean Spaces access keys: scope them, rotate them, stop sharing them

Fundamentals · 5 min read

Toxic combinations: two safe settings that are dangerous together

Try it against your own cloud account.