Product licences and access¶

An organization membership and a product licence serve different purposes. Membership connects a person to the workspace; a licence assigns a product included in the organization's plan. The person's account, membership, branch, commercial coverage and product permissions still determine what they can use.

The backend supports explicit assignment of WorkOS, HiveOrbit and HiveAI. The frontend is still being completed. This explanation does not assume that a particular assignment button is already available; use the inspected membership task guide for the documented screen journeys.

Reserved product names¶

HiveClinic appears in some historical material and reserved product names. Current licensing rules do not grant it through either the live plan catalog or the plan already applied to a workspace. Changing plans, buying seats or retaining an older product flag does not activate a clinical product.

Treat an old comparison table or recognized product name as historical context, not as an available purchase or access grant. This documentation makes no clinical-product release-date or activation promise. WorkOS, HiveOrbit and HiveAI retain their own availability, coverage and permission checks described above.

Who can assign a product¶

A current organization administrator can assign an included product to an eligible member, including themselves. The administrator does not need to hold that product's licence first. This allows an unlicensed administrator to establish product access without treating administrative access as a product grant.

Both the administrator and recipient need active accounts. The administrator must have an active membership and active branch access. The recipient must also be an active, accessible member of the same organization and satisfy the current email-domain policy.

The organization must have usable commercial access, and its applied plan must include the product. A billing-recovery session can let an administrator address a payment problem without making product assignment available. See billing recovery and commercial coverage.

An organization-head designation, job title or product-administrator responsibility does not replace the organization-administrator requirement for this assignment.

How seats are counted¶

A person consumes a licensed seat when they receive their first active product licence. Assigning another included product to that same already-licensed member does not consume a second seat through this operation.

The capacity check counts active memberships with at least one active product licence and also reserves capacity for pending memberships. A person whose branch is inactive can still occupy a licensed seat if their membership remains active and their licences are retained. This count is different from people currently signed in or currently able to enter a product.

For example, assigning both WorkOS and HiveOrbit to one eligible member uses one seat under this rule. Two different members each receiving their first product use two seats. Pending invitations or other pending memberships can explain why apparently unused seats are already reserved.

Assigning a product does not purchase more seats or add the product to the plan. Additional paid add-ons have their own purchase and assignment rules; see membership and add-on access and capacity.

First access for a newly created organization¶

New onboarding records an explicit initial administrator before activation. That initial membership starts without product licences. When provisioning reaches first activation, the initial administrator receives the products included in the applied plan, using the normal licence-grant process.

A workspace still awaiting its initial payment cannot activate directly. Completing payment, finishing provisioning, activating the workspace and obtaining usable product access remain separate stages.

Repeated activation of an already active workspace does not restore a licence that was subsequently revoked. Older organizations without a recorded initial administrator are not automatically assigned one by the migration. Their eligible administrators can use the explicit assignment operation.

What confirmation means¶

A successful assignment confirms the product assignment for the intended organization and member. Repeating the operation for an already-active licence does not create another licence or repeat its access updates.

That makes repetition different from repair. An old successful request is evidence of the earlier operation; it does not prove that a licence remains active after a later revocation or that all downstream access information has refreshed. The existing request reference must not be reused for a different member or product.

A new grant requests updates to sign-in access and billing records. WorkOS also needs its member profile to reflect the change, while HiveOrbit needs updated organization references. These are separate parts of making the assignment usable. The acknowledgement does not prove that an already open session or every product record has updated.

Product permissions remain separate from the licence. A WorkOS licence, for example, is not permission to read every record or approve every request. The assignment does not promote the recipient to organization administrator or bypass a product's own roles, record access or governance checks.

Read permissions, roles and changing access for limited administrator setup grants, tenant knowledge administration, cached role information and session expiry.

If the product remains unavailable¶

Establish which condition is missing: an active account, accessible membership or branch, the correct organization, an included product, usable coverage, spare licensed capacity or the required product permission. Buying another seat does not repair every one of those conditions.

If the assignment is recorded but product access still fails, preserve the organization, member, product, request reference and displayed error for support. The relevant access state and session need reconciliation; repeatedly assigning the same active licence does not replay its synchronization work.

A deactivated member needs the membership restoration process. This product-assignment operation does not reactivate their membership, reactivate their account or move them out of an inactive branch.