Sign in and manage extra verification¶
Draft guide to the intended final-screen experience. The frontend is still being completed. Relevant differences in the current implementation are explained below; live-environment and reader walkthroughs remain pending.
Read how sign-in and workspace access differ if you are setting up access for a team or investigating an access problem.
Before you begin¶
Use the Zerohive address supplied for your environment. You need the email address and password of an activated, active account. You also need access to that mailbox when Zerohive asks for a verification code.
An invitation or a workspace address does not replace account activation. If you have not activated your account, use Activate your new account from the sign-in page. If the account was deactivated, select Request recovery beneath sign-in; the final screen presents this as Deactivated your account? Request recovery. Recovery eligibility and progress are separate from normal sign-in.
Sign in¶
- Open Sign in to Zerohive.
- Enter your account Email and Password.
- Select Continue securely.
- If Enter your 6-digit code appears, open the email for this sign-in attempt, enter its code and select Verify and continue.
- When Your login is ready appears, select Continue to open workspace access.
You may complete step 3 without seeing a code screen when the account does not require extra verification. This is a supported branch of the flow. Opening an organization can still require another verification step under that organization's policy.
A successful account login does not guarantee that a workspace appears or opens. If a workspace is absent, membership or invitation status needs investigation. If it is present but access is blocked, follow the workspace's explanation or contact the organization administrator. Repeating the password step does not grant missing membership or permissions.
The workspace's applied plan and subscription coverage also matter. Follow the billing-access explanation when payment is the stated cause, and the workspace restriction guide for other pauses or unavailable checks. Payment does not automatically remove an administrative pause. A workspace or plan result that cannot be verified is separate from a rejected account password.
If a login code does not work¶
Check that you are using the email address shown for the current attempt and the newest code generated for that attempt. Do not combine a code from account activation, password recovery or an extra-verification setting change with a login challenge.
If the code or pending sign-in has expired, return to Sign in to Zerohive, enter your email and password again, and use the new code. Use different email returns to the credential screen and can also be used to restart the attempt.
The final screen includes Resend code so you can request a fresh code without leaving this step. That part of the current implementation is incomplete: the control does not request a new login challenge correctly. Until it is repaired, select Use different email and restart the credential step. If a new attempt still produces no email, check your mailbox's filtered messages and ask support to investigate delivery. Do not send support your password or verification code.
Turn extra verification on or off¶
- Sign in and open My profile from workspace access.
- Find Extra verification and check its displayed Enabled or Disabled state.
- Change the switch to request the new setting.
- Open the new email for this setting change and enter its six-digit code.
- Check that the confirmation concerns the setting you intended to change, then select Confirm code. On the retry screen, the final design calls this action Try this code again.
- Check the resulting profile state. A code-entry page or error message means the change has not yet been confirmed.
The current working profile labels the confirmation action Enable extra verification or Disable extra verification, depending on your choice. These buttons perform the setting confirmation described above; the final-screen wording is ahead of this implementation.
If that code has expired, the intended Send a new code action requests another code for the setting change. This control also has a known implementation mismatch. For now, return to My profile and restart the setting change. Changing extra verification is separate from Deactivate account; it should not ask you to close account access.
Keep the effects clear: enabling this setting adds a code to future account sign-ins. Disabling it does not remove a workspace's own verification policy, and platform staff will need it enabled to enter the platform console. A failed update should not be interpreted as an effective change.
Continue a session or sign in again¶
Zerohive uses the session's expiry information to decide whether it can continue. The application also rechecks expiry when a background tab becomes active. If the session has expired, sign in again using the account's normal steps.
The final-screen journey has three recognizable stages:
- Checking your session means saved access is being checked; no code or password is requested on this waiting screen.
- If You're back in appears, select Continue to return to workspace access.
- If Sign in again appears with Your session ended, enter your email address and password and select Continue securely. Complete the code step if requested.
Some frontend paths continue directly once the check succeeds. You do not need to find or open a separate confirmation screen yourself.
There is no universal duration you should assume for all sessions. The identity provider supplies credential lifetimes, the frontend maintains its cookie, and the active account/workspace/administrative context affects which credentials are in use. A browser cookie still being present does not prove that access remains valid.
If your account has been recovered after deactivation, use a fresh sign-in. An older browser session or verification code may correctly be rejected even though the account itself is active again.
Switch context or sign out¶
Returning to workspace selection lets you choose another permitted workspace while retaining account sign-in where it is still valid. Leaving an administrative context removes that context from the frontend session. These actions do not create membership or change your assigned roles.
From the access hub, select Sign out. The You're signed out confirmation explains that this device session has ended. Select Sign in again when you want to return. The current access-hub implementation also follows this confirmation path. Do not interpret it as confirmation that every device or identity-provider session has been revoked.
Troubleshooting by the step that failed¶
| What you see | What to check | Next action |
|---|---|---|
| Sign-in rejects the email or password | Correct account address and credentials | Retry carefully or use Forgot password? |
| Account needs activation | Activation has not completed | Use Activate your new account |
| Account is deactivated | Normal login cannot reactivate it | Enter the account-recovery journey or contact support |
| Code rejected | Wrong attempt, wrong purpose, replaced or expired code | Restart the relevant sign-in or setting-change request |
| No code email | Correct mailbox and filtered messages; delivery may be delayed or failing | Start one fresh attempt, then ask support to investigate if delivery remains unavailable |
| Login works but workspace access fails | Membership, permitted email address, organization state and workspace verification policy | Contact the organization administrator with the displayed message |
| Platform console entry fails | Platform-staff access and extra verification requirements | Follow the explicit requirement or ask the platform administrator to review access |
| You return to sign-in after inactivity or reopening a tab | Session credentials may have expired | Sign in again; report a repeated immediate loop to support |
Information that helps support¶
Provide the affected environment, approximate time, which step failed, the visible error message and whether the problem concerns the account or one workspace. Use the support identifier shown on your profile when you can access it. Share only the information the authorized support process requests; passwords, verification codes and browser session cookies are credentials and are not troubleshooting attachments.
Managers and organization administrators should confirm the person's membership and intended workspace before escalating an account problem. Business owners should distinguish successful login from successful product access when validating a rollout. This prevents a sign-in test from being mistaken for proof that the full employee journey is ready.