Use HiveAI with meetings¶

HiveAI has backend capabilities for finding meeting information, preparing changes and directing a person into the meeting or protected file viewer. These capabilities serve different purposes. Reading a plan does not change it; preparing a change does not save it; opening a join flow does not prove that someone entered the room.

Availability: these capabilities are documented from the backend. The frontend is still being completed, and the inspected final meeting designs do not yet establish the full assistant confirmation and recovery flow. Use the meeting guide, session guide and media guide for the intended product steps. Availability in a connected environment still needs verification.

Understand what the assistant can return¶

The assistant's discovery view filters a limited first page. It can miss a meeting that is outside that page even when the person participates in it. Use the normal meeting view to identify the exact plan and occurrence when the assistant cannot find it. Do not recreate a meeting merely because it was absent from an answer.

Meeting artifact reads return metadata rather than recording bytes, transcript text or temporary file links. Open the protected viewer to inspect the actual content. The assistant's meeting metadata tools alone do not establish that it has listened to a recording, read a transcript or verified the meaning of a decision.

Prepare a change carefully¶

The backend action set includes creating instant or scheduled plans, editing plans, publishing, withdrawing and deleting drafts; admitting or denying participants and changing roles; cancelling or ending sessions; starting or stopping capture; and recording decisions, assignments, completed follow-ups and facilitation evidence. Each operation remains subject to its underlying meeting rules.

These assistant mutations require the implemented advanced authority checks, including the person's current workspace identity and Advanced HiveComms permission. A normal meeting operation being available does not automatically establish that its assistant version is available to the same person. Host/co-host checks and contribution-specific restrictions also apply. Access, seats and storage explains the separate eligibility inputs.

Before approving a proposed change in a connected implementation, check the exact workspace, meeting, occurrence, people, roles, time zone, capture choices and intended result. For a contribution, check the actual evidence and the person responsible; an assistant cannot turn a suggestion into verified completion. The follow-up guide distinguishes assignment, completion, independent verification and correction.

The current assistant edit input does not carry the meeting's work attachment, and its backend mapping sends an empty attachment when updating. Changing such a meeting through this path can therefore remove that association. Use a supported editing flow that preserves the association until this boundary is reconciled. Do not assume that fields omitted from a proposal will remain unchanged.

Some meeting changes are checked against a saved version, but that version does not cover every editable field. If another person has changed the plan or audience since the proposal, reopen the current details and prepare a fresh change. A version check is not a guarantee that every visible detail is unchanged.

Verify the result of a saved action¶

Creating a scheduled plan returns a reference to the created plan. It does not also prove that the plan was published, invitations were delivered, an occurrence was generated or a room started. Creating an instant plan likewise remains separate from starting and joining its live session.

For moderation, ending a session or capture, verify the current session and the specific outcome in its supported view. A saved admission or capture result is separate from provider connection, physical room closure and a ready recording/transcript. For contribution actions, verify the recorded fact and any separate completion or evidence receipt; do not infer receiving-system recognition from an assistant response.

If a response is interrupted, reconcile the original action before trying again. The backend retains a result under the original action identity so a repeat can return that result. A completed receipt may record an unsuccessful outcome. A new request can create a new action, so repeatedly issuing the same instruction is not a safe way to recover an uncertain result.

Complete device and file steps yourself¶

Joining, starting and opening host controls use a protected meeting handoff. Opening an artifact uses a protected viewer handoff. The assistant supplies guidance while device choices, media access and temporary file links remain in the protected product flow.

The inspected Final Screen for prejoin shows Check your setup, microphone, camera and speaker choices, followed by Join now. It also explains when the person must wait for host admission. Follow the session guide for that intended sequence. A handoff does not choose devices, bypass the lobby or supply proof that media connected.

An artifact handoff requires the file to be available and the person to retain the relevant access. A later deletion, access change or expiry can invalidate it. Follow the media recovery guidance to obtain fresh authorized access. Keep credentials and temporary links in the protected flow rather than pasting them into the assistant conversation.

The source can report completion after processing the meeting join/start request or creating a file-view session. That is narrower than actual room presence, successful playback or comprehension of the file. Check the visible result in the meeting or viewer. If the assistant has not accepted the completion, do not repeat the underlying action solely to make the conversation show success.

Interpret schedule reminders¶

The current reminder source uses a published, compliant plan's scheduled starting time. It does not expand recurring plans into a complete occurrence calendar or remove a plan merely because a session ended. A meeting whose starting time has passed can therefore appear overdue without establishing missed attendance, unfinished decisions or uncompleted assigned work.

Reminder access is narrower than every meeting participation type: the inspected source selects internal participants with the required workspace/product access. Missing reminders do not prove that a guest or linked-workspace invitation is invalid. Confirm the actual invitation and session through the appropriate meeting flow.

For managers and executives, use these reminders as schedule information. Assess attendance, decisions, assigned actions and verified outcomes from their corresponding records. A reminder count is not a performance measure.

Recover from an incomplete assistant result¶

Share the workspace, meeting/occurrence, attempted action, approximate time and visible explanation with authorized support. Keep protected credentials, file links and unrelated meeting content out of the report. Connected assistant behavior, source authority, receipt recovery and the initial reader walkthrough still require acceptance.