Meetings and transcripts

Meetings become knowledge. A transcript is not a souvenir — it is ingested so Ask and the assistant can cite it.

Find them on the project under Documents → Meetings. Team meetings that cover several clients also live on the org channel.

Live calls (Team)

Start a call from chat (project or team channel — DMs are not transcribed).
Turn Send to transcripts on if you want a record (a manager or the person who started the call). Org settings can turn this on automatically. Studio can still place calls; live capture is Team (and the trial).
Spoken words appear after a short buffer (about 30 seconds of speech). Chat typed in a team channel is saved on the project you are Now discussing.
When the call ends, the transcript lands under Meetings.

Client guests invited from a project conversation bar (see Chat and calls) are labelled by name on the transcript. They do not need a hive account.

Phoenix decides who may join; the media itself is LiveKit (camera, mic, screen share). You do not configure that.

Import a transcript (every plan)

You do not need a LiveKit call.

Open Documents → Meetings.
Paste or upload notes from Meet, Zoom, Granola, or similar.
Wait for ingest. Status on the transcript is the same idea as a file: ready means it is searchable.

This is the path for “we already had the kickoff on Zoom.” After ingest, open the meeting and tap AI digest (next to Re-index) to propose tasks, decisions, and workstreams — the same review cards as a live call. Speaker names in the paste are matched to people in the hive when the name is unique.

Team meetings that cover several projects

An org channel (managers create these in Chat) is a hive-wide room with no single project. A weekly that walks several clients belongs here.

On a live team call, Now discussing is a list of every project you can see, most recently active first. A manager or the person who started the call picks from it; the name updates for everyone in the room. You do not have to choose a project before the call starts. Chat typed in that org channel while transcription is on is saved on the current span, so it shows up under each project’s Meetings tab after the call.

After the call or after import:

Open the transcript.
Split the timeline into spans — “this stretch was Project A, then Project B.” After a team meeting InHive may propose those splits from the talk; confirm them before they become knowledge. Names of projects, people, deliverables, and goals heard in the meeting show as chips. A project chip can start a suggested split. A deliverable or goal chip can link that line. A person chip is only a label — it does not notify anyone. Uncertain chips stay visible and do not act.
Confirm assignments (proposed spans stay off the knowledge base until you confirm).
Re-index so each confirmed span is knowledge on the right project.

Managers can remove individual lines before they become memory. Re-index after you edit — that rebuilds the knowledge base and the short AI summary from what is left. The old summary hides as soon as you tap Re-index, then the new one appears when it is ready.

Simultaneous “we’re on Project A now” switches can conflict; one wins. If a span looks wrong, fix the timestamps and confirm again.

Meeting AI actions (Studio+)

A transcript can propose tasks, decisions, and new deliverables or goals. Those land as proposals — nothing is created until someone approves. Each card shows what it is (task, feature, or decision), its review status, and the suggested fields. Each proposal still needs a quote from the transcript. If it cannot quote, it does not land. An unanswered question in the meeting may land as an unknown decision for someone to resolve.

On a live call this runs when the meeting ends. On an imported transcript or .txt, tap AI digest next to Re-index. A long paste can take a few minutes. If the button still says Digesting and nothing lands, tap it again.

If suggestions fail (the model is busy) or come back empty, use Retry suggestions on a live recording, or AI digest again on an import.

When the meeting introduces a new deliverable or goal and the tasks that belong to it (and maybe a decision), InHive groups them as a pack. Approve pack creates the deliverable or goal first, then the related work, already linked. You can still approve or reject a single card if you only want part of it.

Chat and calls · Documents · Knowledge

When a meeting changes the plan

A settled scope change may appear as one Proposed change. Review change expands in place, showing the source line, proposed agreement, earlier decision it replaces (if any), and before-and-after task or feature updates. Correct the wording with Edit, refresh the review, then Approve this change once. Work and its traceability links apply together. Use the meeting-source link to return to the exact line, or open the combined record in Plan → Plan History after approval. Individual actions and new-feature packs continue to work.