Password recovery¶
Password recovery lets an active account holder replace a forgotten Zerohive password using a code sent to the account's email address. It is an account-level journey: the person does not choose an organization or product while resetting the password.
Local documentation draft. The backend and frontend contain the recovery flow, with implementation gaps described in the guide. The intended steps follow the current final designs. Environment delivery and reader acceptance remain unverified.
What recovery changes¶
A completed reset changes the password used for the existing identity. It does not create a new account, change the email address, restore a deactivated account, grant workspace membership or change product permissions. The person returns to sign-in afterwards and completes any required extra verification and workspace selection.
| Need | Correct journey |
|---|---|
| Forgotten password for an active account | Recover your password |
| New account awaiting activation | Create and activate an account |
| Deactivated account | Account deactivation and same-account recovery |
| Sign-in code, extra verification or session problem | Sign-in and access |
| Profile details or preferences | Account profile |
An authorization PIN for sensitive work inside a workspace is a separate credential. Changing the account password does not update that PIN.
Why the distinction matters¶
For users, the outcome is a usable new password, followed by a fresh sign-in. For managers and business owners, password recovery restores a credential the person already owns; it does not approve access to organizational information. A successful recovery screen is insufficient evidence that the person can perform their work.
Organization administrators should investigate membership and product access separately. Support should identify whether the person cannot receive the code, cannot confirm it, cannot save the password or cannot sign in afterwards. Those failures have different causes and remedies.
The current recovery implementation does not establish a guarantee that changing a password revokes every previously issued session. Suspected account misuse requires the organization's support or security process in addition to password recovery.
Read next¶
Use the step-by-step recovery guide for the intended journey, current frontend differences, password requirements and troubleshooting. Technical and operational details are maintained privately for the responsible teams.
For the separate workspace credential, see authorization PIN setup and replacement. Its email-confirmation journey and implementation limits are documented independently.