Skip to content
VooHr Support Contact Sign in

Team and account

Sign-in, 2FA and password

VooHr supports email/password and Google sign-in paths, and uses time-based one-time codes for two-factor verification in applicable accounts. Password-reset emails are not currently available.

Sign in and password #

Email/password sign-in verifies the stored password hash and starts an authenticated session. Google sign-in is also implemented. If a password is entered incorrectly in the email flow, the application may use an emailed one-time code recovery path for the registered address.

The Forgot password form does not send a reset link or change a password. Its backend responds that password reset emails are unavailable. If you cannot access your account, follow the message shown by that flow and contact the currently listed support address; do not expect an automated reset.

Two-factor authentication #

TOTP setup shows a QR code/URI for an authenticator app. After a valid code is verified, the account stores TOTP settings and generates ten single-use backup codes, shown once. Save those codes somewhere safe; the stored versions are hashed.

During sign-in, a user who has lost their authenticator device can verify with an unused backup code. Each code can be used once. Regenerating backup codes invalidates the prior set and requires an already TOTP-verified session.

  1. Start TOTP setup in the account security settings.
  2. Add the displayed QR code or URI to an authenticator app.
  3. Enter a valid authenticator code to verify and enable setup.
  4. Save the ten single-use backup codes shown after verification.
  5. If the authenticator is lost, use an unused backup code at sign-in.

Keep recovery information safe #

Never send a password, authenticator secret, or backup code in a support request. If you still have an active verified session, review the security settings and regenerate backup codes if needed. Losing both the authenticator and all unused backup codes can prevent access.

Password reset and account recovery policy beyond these implemented paths: [CONFIRM: account recovery process and support contact ownership]

Use this guidance thoughtfully

This page describes the current product workflow; it is not an HR policy or a promise about every deployment. Before acting on information about an employee, verify the source record, consider context the system cannot see, and use your organization's process. If a control behaves differently from this guide, check the current workspace UI and confirm the saved result rather than assuming an action completed.