Currently there are only two scopes for the API tokens, read-only and read-write, but this tokens are extremely dangerous as they affect all the resources in the account without restrictions. For example, create a million droplets or delete all of them.
It would be more desirable to have more control over the scope by choosing the resources it will operate on, i.e. droplets, volumes, floating IPs, etc. And a quota to limit their blast radius in the case of a security incident.
Are we getting something like this anytime?
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!
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.
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.
Click below to sign up and get $100 of credit to try our products over 60 days!