Developer account security

Account security protects the developer’s dashboard identity. It is separate from database-user passwords, which your application uses to connect to an engine.

The dashboard includes account security/MFA screens and a sign-in MFA step. Use the account’s supported security flow and retain recovery information securely when it is offered. These public database API docs do not define an alternative account-MFA API or guarantee that every hosted account-security screen is enabled.

If an account-security action is unavailable, record the screen, UTC time and sanitized error/request ID and contact support. Do not attempt to repair dashboard access by changing database users, disabling application TLS or sharing session cookies.

After suspected exposure, distinguish the credential involved: revoke a developer token, rotate an application database password, or use the account’s recovery/security flow. Review workspace membership and supported audit events as appropriate.

Token management · Database credential rotation · Security practices.