Connect your work mailbox to HiveComms¶

The email assistance explanation covers bounded mailbox reads, reviewed messages and recovery when an assistant result differs from delivery.

HiveComms brings access to your work mailbox into WorkOS. A personal connection uses the work email associated with your signed-in account. Your organization chooses the email service and permitted sign-in methods; connecting a mailbox is a separate action from configuring that organization-wide service.

Availability: The backend implements personal password/app-password connections, provider sign-in, connection status and disconnection. The intended journey follows the current Final Screens. The inspected frontend still shows sample content and navigation controls; it does not establish a working mailbox connection. This draft covers personal connection, reading, sending, recovery and the meaning of work-linked verification. Organization provider/settings administration is described in Set up email for your organization. Email data, exports and account removal explains what is stored, exported or removed and why older mailbox connections may require reconnection. Assistant integration, remaining runtime coverage and verification in a running environment continue separately.

Use Connect, reconnect or disconnect your mailbox for connection steps, and Read messages in your work mailbox for folders, detail, attachments and recovery. Use Send an email and understand its status for the inspected personal compose journey and uncertain-result recovery. Read Email linked to a business task to distinguish sending, source verification, corrections and recorded contribution. Use Recover access to your email provider when reachability, sign-in or organization configuration prevents mailbox access.

Whose mailbox is connected?¶

The connection belongs to the current person within the current organization. The connection request does not let you supply a different mailbox address. Check the displayed work email before proceeding. If it is wrong, resolve the account or workforce information with your administrator; entering another address into an unfinished preview does not change the supported connection.

This is not a shared-mailbox delegation procedure. A manager or support role does not, by itself, give someone access to another person's email. The organization-wide configuration and the person's authorization are both relevant, and successful sign-in to Zerohive alone does not establish mailbox access.

What connection establishes¶

The connection flow checks access to incoming and outgoing mail before saving the connected state. A successful check means that those checks succeeded at that time. It does not prove that every subsequent folder read or send will succeed, that an outgoing message reached a recipient, or that someone read it.

The connection page can show the provider, sign-in method, work email, last validation time and whether action is needed. The saved status is not a continuous live provider-health check. A missing validation time is not evidence that a check happened recently. Token renewal can also update the recorded time before a later mail connection succeeds; it is not proof of a successful current read.

Provider sign-in and app passwords¶

Provider sign-in opens the configured provider's authorization page after a Zerohive authorization-PIN check. You review the provider's request there, then return to Zerohive. This flow uses a short-lived, single-use return. It does not ask you to paste provider tokens or authorization codes into chat.

A password or app-password connection instead validates the credential supplied in the protected connection form. An app password is a provider-issued credential for an application, distinct from the everyday account password in the inspected Google Workspace design. Use only the method enabled for your organization and shown by the connected product.

This guide follows the intended Google sign-in and app-password journey. Microsoft 365 and custom providers are also recognized by the connection service; their screen variants still need verification before this guide can provide their exact steps. The sign-in choices displayed by the finished product must reflect your organization's permitted methods.

If profile details and the connection page disagree, use the profile and status recovery guidance before another sign-in. A saved address, running service and successful mailbox operation are separate facts.

Responsibilities and business expectations¶

Individuals check the work email, complete their own authorization and report unclear outcomes. Tenant administrators maintain the organization's provider configuration and help with account or policy mismatches. Support correlates connection attempts and cleanup results through authorized operational channels without asking for passwords, PINs, tokens or return-link contents.

Managers should allow for reconnection and provider interruptions when work depends on email. Executives should assess the connected, tested experience in the relevant environment before treating mailbox integration as an operational control. A preview, a connected badge or a successful connection check is not a delivery guarantee or a service-level commitment.

Disconnecting is an access change. It is not account deletion, provider-consent revocation, mailbox erasure, or confirmation that every already-started send was cancelled. Coordinate any broader access-removal requirement with the administrator.

For the meaning and limits of recorded outgoing activity, read mailbox email history. Connection success and recorded sending are different facts.