Staging draft Work in progress · For review; coverage and acceptance incomplete

Connect, reconnect or disconnect your mailbox¶

Administrators configure the workspace first through Set up email for your organization. The steps on this page connect one person's mailbox after that setup.

This guide describes the intended WorkOS journey from the inspected Final Screens. The current frontend is a preview: its connection action navigates to sample inbox content. Follow these steps in a connected implementation; a preview transition does not confirm that credentials were checked or saved.

Before you begin¶

You need access to the correct WorkOS organization, the correct work email on your account, an organization-configured mail service and your Zerohive authorization PIN. Depending on the enabled method, you also need to authorize access with the provider or have the appropriate application credential.

Keep the authorization PIN separate from the mailbox password. Enter either only in the intended protected form. Support does not need these values, provider tokens or the full sign-in return URL to investigate an issue.

Open HiveComms, then Mailbox. Check Your work mailbox and Signed-in work email. If the address is wrong, stop that connection attempt and ask your administrator to correct the underlying account information.

If the page says the workspace needs to finish mailbox setup, return to HiveComms and ask the workspace administrator to complete configuration. Repeatedly submitting personal credentials cannot repair missing organization setup.

Connect through the provider¶

The inspected Google Workspace journey is:

On Choose how to sign in, select Continue with Google when that is an enabled option.
On Confirm with your authorization PIN, enter your Zerohive PIN and select Continue to Google. Back returns to the choice without completing the connection.
Review the authorization request on Google's page and approve access only for the intended work account.
Return to Zerohive and allow Finishing your mailbox connection to complete. The incoming and outgoing mailbox checks must finish before connected state is saved.
At Mailbox connected, verify the work email. Select View connection to inspect the saved status or Open Inbox to continue.

A provider approval page and a saved Zerohive connection are separate outcomes. If the return fails, use the recovery guidance below rather than assume either that connection succeeded or that provider authorization was undone.

The backend's default return window is ten minutes, configurable by the platform. Start a fresh flow when the return has expired or already been used. Do not reuse an old return link or share it with another person.

Connect with an app password¶

Use this path only when the organization enables it and the connected product offers it.

Select Use an app password.
Check the fixed work email again.
Enter the app password and your Zerohive Authorization PIN in their separate fields.
Select Connect mailbox and wait for the result. Back leaves the form without establishing a new connection.
Confirm the connected result before relying on inbox navigation.

The connection validates incoming and outgoing access before saving. A successful check in only one direction is insufficient. An unavailable provider, an invalid credential or a disallowed method can prevent completion.

Available sign-in choices depend on your organization's setup. If the offered method does not match the credential you have, ask the administrator to confirm the supported method before proceeding. Do not put your everyday account password into a field that asks for an app password. The preview's editable mailbox and provider fields do not establish that those choices are supported.

Review and reconnect¶

Open the connected-account view to check the work email, provider, method and last check. Treat the time as recorded connection information, not a live guarantee. Token renewal can update it before a later mail connection succeeds; the actual read or send still needs its own result.

When Reconnect your work mailbox appears, check the account and choose Reconnect with Google for the inspected provider-sign-in variant. Repeat the authorization and return flow. Not now leaves the connection unresolved.

An interruption does not imply that mailbox content was deleted. A fresh connection can replace saved credentials while old credential cleanup runs separately. If the page remains inconsistent after the result, ask support to check the saved state before repeatedly reconnecting.

Disconnect the mailbox¶

From Connected mailbox, select Disconnect mailbox.
Review Disconnect this mailbox? and the displayed email.
Enter your authorization PIN.
Select Disconnect mailbox to confirm, or Keep connected to dismiss the confirmation.
Confirm the refreshed disconnected state. If the result is missing or uncertain, reload the connection status and ask support to investigate.

Successful disconnection clears the saved connection details and may request separate credential cleanup. Cleanup completion is separate from the confirmation. The operation does not delete provider mail, revoke provider consent, erase historical activity, recall sent messages or prove that an in-flight send was stopped.

Recover from an unclear result¶

What you see	What to do
Incorrect or missing authorization PIN	Use the correct Zerohive PIN or the supported account recovery process. Do not substitute the provider password.
Sign-in method unavailable	Ask the workspace administrator to verify provider configuration and permitted methods. A method shown in a sample screen may not be enabled.
Provider refuses access or cannot be reached	Follow the provider's access guidance or ask the administrator to check the connection. Repeating the same credential will not resolve a configuration or network failure.
Sign-in link expired or already used	Check the current connection status, then select Start again if a new connection is needed. The failed return alone does not establish that earlier consent or connection work never happened.
Provider approval succeeded, but Zerohive did not confirm connection	Check connection status and seek support if it remains unclear. Provider approval does not prove the later checks and save completed.
Connection or disconnection appears to time out	Check the current saved state before starting another attempt. A lost response and a rejected change are different situations.
Disconnected but earlier sending is uncertain	Ask support to reconcile the existing send. Do not resend merely because the connection was interrupted.
Persistent failure after reconnection	Provide the organization, work email, approximate time and visible error, without credentials or the sign-in return URL.

For delivery and activity interpretation, continue to mailbox email history. Continue to reading messages for folders, detail, attachments and recovery. The personal sending guide explains compose steps and status recovery. Connection success must not substitute for a reading or sending result.