Start with the reset-email option on the sign-in screen when it is enabled. Enter your account email, use the latest reset message and finish the reset in the same browser. If no message arrives, check the address and spam folder, then contact the administrator responsible for your deployment.

​
Administrator checks

Verify that the intended deployment is reachable and that outbound email is configured. Check the account’s authentication method: an account managed by an external identity provider follows that provider’s recovery process. Do not ask the user to send their current or replacement password. Passwords and password hashes belong outside support tickets, screenshots, public websites and shared documents.

​
Database recovery

A database edit is a last-resort operator procedure requiring a verified backup, the exact release schema and a tested recovery runbook. The PostgreSQL configuration example uses database and user sydekyks on Compose service postgres. Other deployments may use different identities; an embedded PGLite deployment is not PostgreSQL. The inspected source hashes local passwords using bcrypt with cost 10. Generate any required hash locally with the release’s supported implementation. Do not enter a password into a third-party hashing website. This preview intentionally does not provide an executable account-update query before account targeting, token invalidation and sign-in recovery have been validated for the selected release. Your operator must test those steps in an isolated copy and record the result before applying their runbook to a live account. See sign-in and account access for user instructions and backup and recovery planning for the recovery prerequisites.