Providing access to droplet without impacting key settings/security

I am the owner to a few droplets. Hers is what:

  1. Allow some developers to access and work on the droplet/database, without myself having to be in the loop, providing second factor authentication codes etc

  2. Can I provide restricted access to the droplet for management purposes with opening up the security/billing/ buying permissions to the developer?

Don’t get me wrong, it is not about trust but to prevent inadvertent modifications

  1. Can we create a team of people to work on one droplet while giving them a view of the other droplets?

Any help will be genuinely appreciated.

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hi @atanum,

If I understand correctly, you are looking at DigitalOcean Teams. Features Teams are useful for project leaders and business owners who want to share control of server infrastructure with developers, financial administrators, and other collaborators.

You can create multiple teams and there is no limit to the number of members a team can have. Each team is billed separately and has its own payment information.

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.

To learn more details, I’ll suggest checking out the documentation on the matter:

Hope this helps!