I need to invoice different clients for different droplets. Currently I have all my droplets under my account, I’ve set up a team for each of my clients but then find out that there is no way to move droplets between teams. This is a problem, it should be possible to do this so that the droplets can be grouped into different invoices. I know I can recreate a droplet from a snapshot, but it’s not smooth, result in changed IPs etc..

I agree that this would be a very nice feature. Like others have mentioned, I have a server on my account for a client that I would like to transfer to a team for individualized billing. Setting up a new server with a new IP would require a lot of updates for various implementations.

Hi,

What I need is to selectively transfer some Droplets to a Team.
Actually, I also need to transfer some Domains, Volumes, Snapshots, etc..
When I created the team, the only option available is transfer EVERYTHING, which is not an option for me, as my account runs several non-Team resources.

Do you plan on supporting or working on something like this?
Selective transfer of some resources like Droplets, Domains, Floating IPs, etc. to another Team?
I won’t mind even if this is a manual process and I need to submit a support ticket.

Thanks!

I completely agree. I was hoping to split up all the droplets I had to teams related to different clients. The way it works now is nice for new clients, but shame we can’t use it with our old clients. Snapshotting and killing just isn’t an option with the downtime or branching data that will create.

Same for me, I have to group my droplets under individual teams in order to get separate invoices. I need to pass the invoices on, and each client should pay for only their droplets. Please make it possibme to transfer between teams without the hassle of rebuilding from a snapshot and getting new IP (I can live with getting a new IP is I must), but don’t like to have to destroy and recreate each droplet.

Another option could be to simply allow for droplets to be grouped under tags or folders, and then have the option to group these into individual invoices. The invoicing issue is probably often the reason people need teams, more than the actual authentication thing, so this could solve it for those that just needs to separate invoices.

I recently created a team and now I wish to transfer several droplets into the team as different teams need to have different access levels.

I think the key takeaway to consider is:

Given that a team’s roles are dynamic and can change overtime, shouldn’t droplets be able to change teams as well?

A lot of brilliant use cases have already been presented above.

I think that in order for permission systems to be effective, a group within a system needs the ability to be flexible as to a.) it’s members and b.) it’s assets.

I think the DO team got the members part down pat and it would be really nice to have the assets (droplets) part in place as well.

If I were to take UNIX file permissions as an example, it’s great that I can add/remove users from groups and edit permissions per group but I think it would be very tedious if I’d have to recreate a file just to change it’s group.

Nonetheless, thank you DO team and love your excellent platform!

This would be extremely valuable for us as well, especially in the case of spaces

Its 2020, and looks like this feature still isnt available? Can DO team tell me how can we achieve this without downtime or just provide a way to differentiate invoicing and billing?