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

Zerohive glossary¶

This glossary explains the shared language used across Zerohive. Start here when a word has a different meaning in another product or in your organization. Follow the linked guide for the exact rules, steps and current limitations.

Draft status: These definitions summarize the reviewed feature guides. They do not establish deployed availability or complete platform coverage. A named role describes a responsibility; reading its documentation does not grant that role or its permissions.

Accounts, organizations and access¶

Term	Meaning in Zerohive
Account	A person's sign-in identity and account-level information. The same person can have different responsibilities in different workspaces. See account access.
Workspace	The organization's working context, with its own membership, policies, commercial arrangements and business information. Changing workspace changes the context in which you act. See workspace selection.
Tenant	The technical term used for the organization boundary behind a workspace. It does not mean an individual employee or a product subscription by itself. See workspace creation.
Product	An area of capability, such as WorkOS, HiveOrbit or HiveAI. Eligibility for a product and permission to perform a specific action are separate. See product access.
Member	A person with a membership relationship to a workspace. An invitation, an active membership and a product grant describe different stages or decisions. See membership.
Workforce or staff record	Organization-specific information about a person. Its identity and lifecycle are separate from the person's shared sign-in account. See People.
Platform staff	Authorized people who administer or support the Zerohive platform. This is different from being an employee or administrator of a customer workspace. See staff administration.
Branch	A grouping of workspace members by physical location. It is distinct from a department, reporting line or job position and does not create a separate workspace. See workspace structure.
Organization head	A designated leadership responsibility maintained through workspace administration. Related approval-body membership can be synchronized separately; a saved designation does not prove immediate downstream completion. See organization structure.
Role	A named set of responsibilities or access assignments in a particular context. A role in one product or workspace does not automatically confer authority everywhere. See roles and access.
Permission	A specific allowed operation or access scope. Current membership, policy, resource state and other checks may still affect whether the operation succeeds. See permissions.
Entitlement	Commercial eligibility for a product or capacity under the organization's arrangement. It does not grant every member every operation. See usage and entitlements.
Session	A period of authenticated access represented by the platform's sign-in state. Expiry, sign-out or changed security conditions can require authentication again. See sessions.
Authorization PIN	An additional secret used for supported protected actions. It is distinct from the sign-in password and does not replace the action's permissions. See authorization PIN.
Signature enrollment	Establishing or replacing a person's recorded signature. Having a signature on file does not grant authority to sign any particular document. See signature enrollment.

Work and decisions¶

Term	Meaning in Zerohive
Workflow definition	A reusable description of a process, its inputs and steps. Drafting or publishing a definition is different from submitting an individual request. See workflow authoring.
Request	An individual piece of work submitted through a supported process. Its progress and decisions follow that process's rules. See requests.
Workflow instance	The running or retained execution of a workflow for a particular request. It has its own progress and history, separate from the reusable definition. See workflow execution.
Task	A unit of responsibility within work, such as a pending review. Completing a task does not necessarily complete its whole request or a receiving process. See task handling.
Approval body	A configured group with membership, a chairperson, voting and signing responsibilities. Creating the body does not create a request or record an approval. See governance authority.
Quorum	The required number of eligible voting members for the body's rules. Direct signers and total members are not interchangeable with eligible voters. See approval-body readiness.
Signing delegation	A time-bounded authority for another person to sign through a member's authority. It does not by itself add voting membership or place a signature on a document. See delegation.
Deadline or SLA	A configured timing expectation for work. Its calculation, working calendar, escalation and enforcement depend on the relevant process. It is not a universal guarantee that every task will finish by that time. See deadlines.
Escalation	A configured response to timing or responsibility conditions. The resulting notification, assignment or other action depends on the process and its current authority. See escalation.
Handoff	A transfer or preparation of work for another responsible area. Sending, receiving, accepting and completing the work can be distinct outcomes. See request handoffs.
Project	A structure for coordinating delivery, participants and progress over time. Its lifecycle is separate from related workflow requests. See projects.
Case	A structure for handling an issue through investigation, responsibilities and outcomes. See case management.
Correspondence	Memos and official letters handled through their defined preparation, routing and decision processes. A discussion message is not automatically official correspondence. See correspondence.
Shared work	A governed exchange between connected workspaces. The sending and receiving organizations retain distinct responsibilities, data and outcome states. See shared work.
Enterprise network	A relationship between eligible workspaces for defined administration and collaboration. Linking workspaces does not grant unrestricted access to their information. See enterprise networks.
Activity history	Recorded events associated with supported work. Its scope, retained details and retention rules matter; an empty history does not establish that nothing happened. See activity history.

Documents and communication¶

Term	Meaning in Zerohive
Record	Information registered and managed through Records with its own metadata, access and lifecycle. Uploading a file elsewhere does not automatically establish that registration. See Records.
Dossier	A grouping used to organize related records. Membership, purpose and automatic preparation depend on the supported dossier type. See dossiers and archives.
Classification	A governed description that affects how information is organized or handled. Records classification and sensitivity controls have their own rules; a label alone does not prove permission. See Records governance.
Retention	Rules and conditions governing how long information is kept and what may happen afterwards. A date passing or an item entering a queue does not by itself prove that content was deleted. See Records lifecycle.
Document session	An authorized, bounded context for a supported upload, view or signing operation. Different operations can require different checks and outcomes. See document handling.
Conversation	A communication space with its own participants and access rules. Membership does not grant every participant authority to approve the business work being discussed. See messaging.
Meeting	A collaboration event with its own scheduling, participation and integration behavior. Attendance does not by itself record a business approval. See meetings.
Connected mailbox	A supported external mailbox connected under its provider and access requirements. Connection state and message-delivery state are separate. See mailbox integration.
Notification	An update that draws a recipient's attention to an event. Attempted delivery, delivered content, a read receipt and completion of the underlying work have different meanings. See notifications.

Contribution and recognition¶

Term	Meaning in Zerohive
HiveOrbit preparation	Establishing the draft rules and organization information needed for setup while preserving existing choices. Preparation does not itself enable scoring. See initial setup.
Activation or admission window	A reviewed time interval in which work can qualify for HiveOrbit processing, subject to current prerequisites and the event's own eligibility. It is separate from a chart's selected period. See eligibility and recovery.
Pending, excluded and completed evidence	Distinct processing outcomes: evidence can await required checks, fall outside eligibility or finish the processing recorded for its receipt. Receiving evidence does not mean it has produced a score or award. See retained evidence.
Contribution evidence	Recorded information from a supported work source used in contribution processing. Its identity, eligibility, attribution and completeness matter; raw activity volume is not a complete measure of value. See contribution sources.
Contribution measure	An interpreted view of recorded work under applicable definitions, periods and scope. Read it alongside source coverage and calculation limits. See insights.
Recognition points	Values arising from the applicable recognition rules. They are distinct from productivity measures and do not by themselves establish an award or a payment. See recognition and evidence.
Recognition or award	A recorded recognition outcome under its qualifying rules. Display, eligibility, evidence and later fulfilment can have separate conditions. See recognition.
Role profile	Configured expectations and context for a role in HiveOrbit. It is different from a security role that grants product permissions. See HiveOrbit configuration.
Reporting period	The day, week, month or year used for a particular view or process. Its calendar and boundaries affect interpretation; different products' periods need not match. See insight periods.
Source Health	A view of available source observations, coverage and processing conditions. A recent timestamp or an empty result does not prove complete collection. See Source Health.
Reconciliation	A comparison of retained information to detect missing, inconsistent or pending work. A successful comparison does not independently prove every external business fact or calculation. See reconciliation.
Correction	A recorded change to earlier information. Its effects on calculations, recognition and dependent views must be checked separately; do not assume every historical result was rebuilt. See correction evidence.

Governed assistance¶

Term	Meaning in Zerohive
Grounded answer	An answer informed by permitted source information. Grounding helps the reader inspect evidence; it does not guarantee that the answer is complete or correct. See grounded answers.
Citation	A reference to information used to support an answer. Access, version, freshness and the relevance of the cited passage still need checking. See citations.
Personal memory	Personal context saved under the assistant's explicit controls. It has ownership, use and deletion rules distinct from shared work knowledge. See personal memory.
Shared work memory	Shared context used under its own authority and lifecycle rules. It should not be confused with a private personal memory or a published organization manual. See shared work memory.
Workspace knowledge	Organization material prepared for governed assistant use through processing, review and publication. Uploading or processing a manual is not the same as publishing it. See workspace knowledge.
Governed action	A supported proposed change subject to the required authority, review, approval and execution checks. Approval alone does not establish that the source product completed the change. See governed actions.
Provider and model	The approved service and model used for an assisted capability. Configuration, approval and a working provider connection are separate requirements. See providers and models.
Credit	The unit used for applicable HiveAI spending. Available credit, a budget, a reservation and final reconciled usage have distinct meanings. See credits and usage.
Budget	A spending control for its defined scope and period. A budget does not itself supply prepaid credit or override permissions. See budgets.
Secret-access exception	A scoped and governed exception concerning Secret-classified content. It is not unrestricted access to every protected source. See exceptions.
Private Cloud	The implemented private capability boundary described in the source. It and its private provider/retrieval paths remain disabled; documentation is not an activation instruction. See Private Cloud.

Commercial arrangements and lifecycle¶

Term	Meaning in Zerohive
Plan	An offered set of commercial terms, capacity and eligibility rules. The actual offer or contract controls; sample screen prices are not a current price list. See subscriptions.
Subscription coverage	The current plan and term that can permit product use at a particular time. Personal access, product assignments and permissions still apply. See coverage and access.
Renewal grace	A limited period after paid coverage ends when a currently usable saved automatic-payment method and the other required conditions permit continued access. It is not an extension of a trial or proof of successful renewal. See renewal grace.
Saved payment method	A provider-backed payment method recorded for supported automatic charging with consent and current usability checks. It is not a completed payment or permission to charge for any purpose. See payment methods.
Billing recovery access	The narrower access an eligible workspace administrator can have to investigate or manage billing when ordinary products are unavailable. It does not grant product use or bypass account and membership checks. See billing access.
Applied or scheduled plan change	A plan change already in effect versus one recorded for a later effective time. Payment, scheduling and the current access decision are distinct. See plan changes.
Licensed seats	The recurring seat quantity recorded for a workspace's subscription. This is not the number of people currently signed in or automatically a count of unused invitations. See capacity.
Usage	Recorded consumption for a defined measurement and period. Missing samples, filters and collection boundaries can affect the figure. See usage measurement.
Payment and application	A successful payment and application of the purchased change are separate stages. Check the subscription or original workflow when the outcome is uncertain. See billing recovery.
Suspension	A workspace access/lifecycle condition whose cause determines the recovery route. Payment recovery can lift a billing suspension but does not lift an administrator or support pause. It does not mean that the workspace's data has been erased. See workspace lifecycle.
Account deactivation	A decision affecting a person's account. It is separate from suspending an organization or deleting all of its information. See account lifecycle.
Export	Preparation of information within the export's documented scope. Completion does not establish that every external provider or every kind of platform data is included. See data lifecycle oversight.
Deletion	A governed data-lifecycle operation with service, storage, retention and completion boundaries. A submitted deletion request or completed participant does not prove universal erasure. See data lifecycle oversight.

Read a result or an availability statement¶

Term	What to look for
Accepted or queued	The system has acknowledged or scheduled work within the specific operation's rules. Check its later result before treating the business action as finished. See workflow execution.
Pending or processing	Some work remains underway or unconfirmed. Use the original item and recovery instructions; repeated submissions can create a second operation. See governed-action recovery.
Snapshot	Information representing a particular observation or retained state. Check when it was captured, its scope and whether later updates have arrived. See insight interpretation.
Audit evidence	Retained information about supported actions within its documented coverage. It does not automatically provide a complete history of all events or certify compliance. See platform oversight.
Draft documentation	Content under review. Source checks, design inspection, deployed verification and reader acceptance remain separate. Each feature states its current limits.
Intended journey	The action sequence described by the reviewed final-screen design. It can be ahead of the unfinished frontend; consult the feature's availability statement.
Implemented backend	Server behavior exists in the reviewed code and configuration. This alone does not establish a connected browser interface, provisioned provider or working deployment.
Environment availability	What actually works in a particular installed environment. Source or design evidence alone cannot establish this.

Return to the platform overview or use the capability map to find a complete explanation.