Security

Please add public API endpoints for team membership and roles so that you can automatically read and update team members via API, incl. via integrations. Right now this can only be done in the control panel. The scopes already exist (team_membership:read/invite/update/delete, role_management:read), but there's no endpoint for these. The endpoints we'd like: List members across an organization List members in a team, with their role, status, and sign-in method List, create, and revoke invitations for a team Change a member's role in a team, including to a custom role Remove a member from a team List roles, with each custom role's permissions Please make these work with OAuth apps as well. Note that Paperspace already has similar endpoints. Thanks!

When creating an API token, allow users to restrict DNS permissions to specific domains or DNS zones. A common use case is Let’s Encrypt DNS-01 validation. An ACME client temporarily creates a TXT record to prove control of a domain. With DigitalOcean, a token granted domain:update can modify DNS records for every domain accessible within the team, even when the client needs access to only one zone. For example, users should be able to create a token with permissions such as: Read and update DNS records Limited to example.com No permission to create or delete domains No access to other DNS zones or DigitalOcean resources Zone-scoped tokens would follow the principle of least privilege and significantly reduce the potential impact of a leaked or compromised API token. This would be particularly valuable for ACME clients, external-dns, CI/CD systems, and other automated DNS integrations.

Hello Support Team, I am writing to report a copyright infringement taking place on your network. An unauthorized private server is currently operating on IP address 165.232.122.114 for the game "Little Empire" (developed by Camel Games). This server interacts with modified/cracked APK clients to bypass official game authorization. Details of the Report: Game Title: Little Empire Rights Holder: Camel Games ( https://www.camelgames.com/game/LITTLEEMPIRE ) Target IP: 165.232.122.114 Infringing APK Link: https://www.mediafire.com/file/nvr2lxktsf2flmy/littleEmpire_1.27.8.apk/file I request that you review this server's activity and take the necessary action to address this violation of intellectual property rights. Thank you for your time and assistance.

I would like to be able to setup OIDC with Google. This enables us to enforce logging in with an Google account. It would also be very convenient if we have the option to choose between the functionality to automatically create accounts if they don't exist or to not create them. Currently Digital Ocean accounts are being created if they don't exist, whereafter these will be added to the team. This is not always convenient.

There are companies that outsource their development work and would like to give ACCESS TO SPECIFIC PROJECTS AND DROPLETS ONLY instead of all the projects and droplets. The custom roles allow you to restrict a reole but does not allow you to select the projects or resources so you cannot limit anyone's access to specific resources. It would be a great idea to be able to select specific projects and resources only

test110

The interface shouldn't force what permissions we use. Twice I've been forced to add scopes that my process didn't use. We should be able to bypass this. The error message seem to be sufficient for those who are missing permissions as I discovered when droplet:create permissions didn't force me to create ssh_key:read .

Hello, someone is trying to ban my website, using your services. Please delete this page: https://mcbgugel.sgp1.cdn.digitaloceanspaces.com/durusala.html

Teams should be able to enable and disable per-user access for individual projects. This would be in line with best practices, following the principle of least privilege and maintaining a consistent level of separation between project staff.

Other competitors offer "Escrow as a service" to give access to cloud resources to clients or other stakeholders in the event of a disaster. Can we expect such a feature? Or in the marketplace?