DO Ideas 2

Re-approach the way Teams are implemented.

In reply to

The current implementation of "Teams" seems to be entirely counter intuitive and makes using them ineffective. I'd wager that the majority of accounts created on Digital Ocean were/are created by developers -- their own personal account, plus accounts for their clients.

Personally, I have set up a multitude of client accounts on DO, each with their own account. I currently use a third-party application to keep track of the login credentials for each client and sign into their account to manage their resources.

It would seem that a proper implementation of "Teams" would allow me to switch my client's accounts to Teams and add my own account to my client's teams, so that I can log into my own account and see/manage all of my clients' resources, in addition to my own, within one session -- not force me to log into multiple sub-accounts. That is what is currently required, and it doesn't fix the issue -- it just limits my access while still requiring me to manage multiple accounts for access to my client's droplets.

A brief summary of desired Team features:

- UserA is a developer and has their own droplets for their own applications, and recommends Digital Ocean to a new client, UserB.
- UserB creates an account and makes a team -- UserB is the Owner of the team.
- UserB invites UserA to the team.
- UserB accepts the invitation and is able to manage the team's resources within their Digital Ocean control panel
- UserA is able to be a part of multiple teams from multiple users, e.g. they recommend DO to another client, UserC, who does the same thing.
- UserA should be able to manage the resources of all teams they are a part of by logging into their Digital Ocean account. Adding something like "Change Team View" to the Droplets page would be necessary.

  • ben
  • Sep 11 2018
  • Shipped
  • Sep 11, 2018

    Admin Response

    Hey Ben, Thank you again for your feedback. We recently launched some new features for Teams that should help. The feature highlights include the ability to be a part of up to 10 teams at a time while having your own personal account. new navigation to help quickly switch between teams, separate invoices per team, new Billing role, and unlimited members per team. You can check out the announcement here: And a tutorial here: We really appreciate everyone who provided feedback. Thank you!
  • Attach files
  • Phil commented
    September 11, 2018 16:48

    "ability to be a part of up to 10 teams at a time"

    Why ? I can't have more than 10 clients ? :)

  • Steven Stanton commented
    September 11, 2018 16:48

    I agree with this completely. The way this was deployed feels very half thought out and unfinished. For me it is completely unusable as it just adds to the confusion of logins with multiple clients. They should look at how Twilio has this implemented.

  • Safeharbour commented
    September 11, 2018 16:48

    There is a 3rd party alternative, with more flexibility, and with finer grained permissions:

  • Roman Gorodeckij commented
    September 11, 2018 16:48

    Github approach is all DO needs in here. Simple as that, just add currently existing member to the team, and share some droplets. And I hope you'll never go with monstrosity which AWS did, their user management is most terrible I've seen in history of IT industry. Github did this in a best way possible to imagine, I hope you guys will choose a right side..

  • Sheila Ruth commented
    September 11, 2018 16:48

    Yes, THIS! This is exactly the reason I came to the UserVoice forum. I recommended DO to a client and asked them to set up an account and invite me to their team. When they did, using the email address I use on DO, the invitation email I received told me I needed to use a different email address since I was already using that one on DO. I'm a freelance developer and want to be able to recommend DO to clients and use ONE account to manage all my clients. I opened a support ticket and they recommended I come here. Please implement this! I don't want to have to have a separate account for every client.

  • Manoj commented
    September 11, 2018 16:48

    I'm looking/expecting some thing similar to godaddy's pro program... It allows a developer to manage his/her clients server/domains in one place(single account).

  • Mark P commented
    September 11, 2018 16:48

    Exactly this. I've had this same problem with other hosts too. Implementing this might give you a bit of an edge.

  • Chad Maocn commented
    September 11, 2018 16:48

    Following up...I just tried the user+teamname@domain method mentioned in one blog. It still doesn't allow us to have one account admin more than 1 team, so still pretty useless.

  • The Digital Orchard commented
    September 11, 2018 16:48

    Attempting to delete the Team, since it had zero members and no use for me, it required that I first delete all droplets! Hello? Who in their right mind thought that was a good idea? :)

  • The Digital Orchard commented
    September 11, 2018 16:48

    At the moment, there's zero distinction between a Team within an account and the Account itself, aside from billing access. When I set up a team in the name of a client, that name then appeared as the primary name on my invoices! That's definitely not what I wanted! (unless my client was happy paying for my 20+ droplets!)

    A team should be a sub-group, not overriding the master account in any way, shape or form.

  • Chad Maocn commented
    September 11, 2018 16:48

    I was also let down by trying this. I even had started making plans with a close friend/client assuming this functionality would be what the obvious need was. And then had to change our plans and apologize for DO, so my friends first impression of DO is that it lets you down. If these are known limitation and implementations please tell us that up front. There is no way for us to find this out until we have our client email us the invite to their account and then we find out we can't use our DO account to manage it? What? We need to create a new account? I was hoping I could transfer my droplets to them and stuff. Now I need to create a sub account invite myself to join my team? Send droplets to myself on my other account that I don't need or want and still need to keep track of, and then log back into that alt account to send the droplet to my client/friend. And anytime I want to roll a new droplet to them that I have been working on, I have to do the whole process again. And like I said, we don't find out about this limitation until we've already started talking to somebody about it. We've thought about how we can start using teams, how we can manage them and how this will let us now start promoting DO to our friends because we can login and help them. Nope, SOL. Please fix ASAP. And also please explain known limitation to us, or create a beta program and invite us or something. We are going to be your biggest marketers if you give us the tools to. I saw like 10 people within a month all agree about how disappointing this new feature was.

  • Jeff commented
    September 11, 2018 16:48

    indeed! This is just plain stupid. It would qualify as a hack, and not a really fleshed-out implementation the way things are done now.

  • Juan Lebrijo commented
    September 11, 2018 16:48

    I am a freelancer who works for several clients (each client has his own account).

    Also I have my own account for my own droplets.

    Bug: I need to create an account for each client to join their teams.

    Feature: One account should belong to many teams