Meetings¶
HiveComms meetings bring people together for a conversation now or at an agreed time. Organizers choose the people, their roles, admission rules and whether recording or transcription is allowed. A meeting can also be associated with work elsewhere in the platform.
Availability: this is a source-reconciled draft. The intended journey follows WorkOS 06 Final Screens. The frontend still contains sample views and navigation without connected saving, publishing or room entry. Backend authoring is implemented, but a successful design review, working deployment and reader acceptance are not established here.
Start with create and manage a meeting, then join and host a meeting. If you received an invitation link, use the guest entry guide. Use recordings and transcripts to find a saved file, understand its readiness and request viewing access. Decisions, actions and evidence explains accountable follow-up and the contribution interfaces still needed. Meeting updates in your inbox and meeting activity history explain the related notifications and recorded actions.
Choose the right kind of meeting¶
| Choice | Use it for | What it establishes |
|---|---|---|
| Meet now | A conversation you want to begin immediately | An instant meeting still needs people, access checks, publication and a successful room start. Creating its record alone does not open a room. |
| Schedule for later | A conversation people need to prepare for | A saved start and end time, time zone and optional repeat setting. Saving or publishing does not prove that future rooms will open automatically. |
| One-to-one | An organizer and one invitee | Two people in the meeting, including the organizer. |
| Group | An organizer and at least two invitees | Advanced meeting access is required for the participating workspace members. |
The meeting's saved plan and an actual live session are different things. One meeting can have session records. A recording or transcript belongs to a session and has its own processing and access state. A Published badge does not mean Live, and an allowed recording setting does not mean a recording exists.
People, roles and access¶
Meeting access, seats and storage explains the independent access inputs, delays, capacity and federation checks, missing storage information and recovery when a summary or eligibility result disagrees with an administrator's change.
The organizer is a host. Hosts and co-hosts can edit, publish and withdraw the meeting; ordinary attendance does not grant those controls. A management job title or administrator title is not, by itself, a meeting role.
People from the current workspace need active membership and WorkOS access. A simple internal one-to-one meeting without recording or transcription uses basic meeting capability. Groups, named guest participants, people from linked workspaces, recording and transcription require advanced capability for the evaluated internal and linked-workspace participants. Guests are a different participant category; adding an external email address does not grant workspace membership or host authority.
Linked-workspace participation also depends on the enterprise relationship, current workspace state and trust policies on both sides. Seeing a connected workspace or a person's name is not a guarantee that the meeting will pass its current access checks.
When existing advanced seats can cover missing assignments, an authorized administrator can resolve those assignments through the appropriate administration flow. If purchased capacity is insufficient, the purchase decision belongs outside meeting setup. This page does not quote a price or treat a readiness check as a purchase.
Understand saved states¶
| State or signal | Meaning | What to check next |
|---|---|---|
| Draft | The meeting plan is saved without publication. | Review the complete people list, roles, times and policy. Draft is not a promise of private visibility. |
| Access needs attention | Required participant access or advanced assignments are not ready. | Resolve the specific issue and check readiness again. Some access failures prevent saving altogether. |
| Published | Publication was accepted for the meeting plan. | Confirm the correct saved meeting. Notification delivery, a live room and attendance are separate outcomes. |
| Withdrawn | The publication state was changed to withdrawn. | Check affected sessions and participant communications separately; withdrawal does not itself establish that a live room ended. |
| Live | A session has started. | Room entry, admission and recording are separate checks. The meeting list alone is insufficient evidence. |
Editing does not always return a published meeting to Draft. Existing publication can be retained when the updated meeting remains eligible. Review the resulting state after each save rather than assuming a separate approval or publication step will protect every edit.
Read Use HiveAI with meetings for assistant information, reviewed changes, device/file steps and uncertain-result recovery.
Business value and practical limits¶
For teams, a meeting plan makes its purpose, people and access choices easier to coordinate. For managers, roles clarify who can govern a session. For executives, meeting records and activity history can support follow-up, but a participant count is an invitation count, not verified attendance, productivity, agreement or a completed business outcome.
The current meeting list is not established as an invitee-only view. Its source does not itself limit the list, details or editing-context reads to the invited people. Avoid putting confidential material in titles or assuming an unpublished plan is visible only to its organizer. Access boundaries require further implementation and environment acceptance.
The design includes purpose/preparation text, richer people selection and a repeat choice. The inspected authoring contracts do not save purpose/preparation text; repeat settings alone do not establish automatic occurrence generation. These differences remain explicit in the guide.
Storage limits can block creation and publication as well as live meeting activity. A missing local quota projection is not proof that storage is unlimited. Recording, transcription, provider readiness, guest-link delivery and saved artifacts require their own successful operations.
Coverage still being completed¶
This draft covers meeting plans, authoring, readiness, publication, editing, withdrawal, draft deletion, current-member live sessions, guest-link entry, recording/transcript files, contribution facts and access information. The session guide distinguishes saved admission/roster state from actual connection and provider closure. The guest guide explains identity, expiry and session limits. The media guide separates capture, file readiness, ownership, retention and temporary access. The follow-up guide explains decisions, assignments, completion, independent verification, corrections, the session ledger and delayed-summary recovery. The access guide explains separate authority updates, capacity, storage, federation and summary freshness. Working invitation issuance/revocation, transcription production, connected controls and physical retention remain unproven. The assistant guide covers backend reads, twenty mutations, protected steps and reminder meaning, with authority/receipt/device limits explicit. Meeting information, exports and deletion explains the workspace lifecycle contribution, saved files, other owners and uncertain-result recovery. Receiving-system and platform coordinator reconciliation, source refresh and connected assistant/runtime acceptance remain unfinished. The feature remains partially documented and unaccepted until those scopes and the initial reader walkthrough are complete.