Conversations
Understand how Conversations ingests meetings and controls transcripts, summaries, action items, sharing, access requests, and provider connections.
Conversations is Infra One’s organization-scoped workspace for meeting records from Krisp and Granola. Current non-guest organization members can find meetings they are authorized to open, review transcripts and summaries, and work with shared notes and action items.
It is not an organization-wide recording archive. Opening a Conversations workspace and opening one meeting are separate access decisions. In particular, an organization administrator does not gain access to every private meeting.
How meetings arrive
| Provider | Transport | Meeting data |
|---|---|---|
| Krisp | Inbound transcript_created and note_generated webhooks | Speaker-attributed transcript data and an optional recording can arrive separately from the summary, outline, and action-item data. Conversations merges the two event types in either order. |
| Granola | Scheduled polling of completed notes | Conversations stores the completed note’s transcript and summary. A new connection begins with a 30-day window and then polls incrementally. Granola does not provide the speaker diarization used to render utterance-by-utterance transcript rows. |
Provider ingestion creates or updates the meeting record. A Krisp note_generated delivery can also add parsed action items, and ingestion can evaluate whether a private meeting qualifies for organization-wide visibility. User-triggered AI summary generation is a separate action; ingestion does not automatically run it.
New meetings start Private. A Team-wide connection changes provider attribution, not visibility, so it does not make the resulting meeting available to the whole organization.
Find meetings and work
After Conversations selects an organization, the workspace exposes these surfaces:
| Surface | Purpose |
|---|---|
| All meetings | Browse every meeting that the current viewer can open. Search covers title and summary, and filters cover access, visibility, provider, owner, participant, tags, CRM state, date, and star state. |
| Org meetings | Open the meetings browser with Org-visible visibility already selected. |
| My meetings | Open the meetings browser with Yours access already selected. |
| Shared with me | Review meetings that another member explicitly shared with the viewer. |
| Activity | Review recent accessible meeting and share activity. |
| Action items | Search and update action items from meetings the viewer can open. |
| Connections | Review and manage the Krisp and Granola connections available to the current user. |
A meeting detail page has three tabs:
- Transcript shows speaker-attributed utterances and talk time when the provider supplied them. Recording appears when the meeting has a stored recording reference; playback uses an authenticated Infra One proxy, so the provider URL is not exposed and playback success remains a separate check.
- Summary shows the current summary and outline, plus shared meeting notes. An authorized user can request a new AI summary when AI features and transcript text are available.
- Action items shows open and completed tasks. Users who can open the meeting can add, extract, complete, reopen, and delete these meeting-level items.
Stars, tags, notes, summaries, and action items belong to the meeting. They are not personal annotations or per-user bookmarks.
Workspace and meeting access
Conversations first resolves the workspace from trusted organization membership:
- guest memberships do not produce a Conversations workspace;
- one available organization is selected automatically;
- with multiple available organizations, the root page shows Select an organization and Open organization selector;
- an organization slug in the URL is accepted only when it belongs to the signed-in user’s available workspaces.
Inside that workspace, a current member can open a meeting when at least one of these conditions holds:
- the meeting is Org-visible;
- the member owns it;
- the member attended it as an organization member;
- another authorized member explicitly shared it with them;
- for an administrator only, the meeting is strictly unassigned: it has no owner and no attendee was ever an organization member.
The final administrator rule is narrow recovery for a meeting with no owner and no attendee ever classified as an organization member. Existing explicit shares are separate access paths, and administrator standing by itself does not grant other private-meeting access.
Visibility and access classifications
Visibility describes who else may open a meeting. The access classification describes how the current viewer reached it. The two values are deliberately separate.
| Classification | Meaning |
|---|---|
| Private | Current owner and member attendees retain access, as do explicitly shared current members. |
| Org-visible | Every current non-guest organization member can open the meeting. |
| Yours | The viewer owns the meeting or attended it as an organization member. |
| Org | The viewer reaches it through organization-wide visibility and not through Yours. |
| Shared | The viewer reaches it through an explicit share and not through Yours or Org. |
| Unassigned | An administrator reaches a strictly unassigned meeting through the narrow recovery rule. |
The access classification uses that precedence: an owner of an Org-visible meeting is classified as Yours, and an explicitly shared organization-visible meeting is classified as Org. At the reviewed revision, the meetings table renders Yours in its Access cells; Org, Shared, and Unassigned remain filter classifications rather than visible cell labels.
Meetings begin Private. Automation can publish an eligible meeting to the organization, but it never automatically makes a visible meeting private. A person who selects Make private pins that decision so automation does not publish the meeting again.
Writes, notifications, and deletion
Meeting access does not imply management authority. Only a current owner or a current organization-member attendee can change visibility, manage explicit shares, or delete the meeting. A narrow administrator fallback can answer an access request when no current owner or current member attendee remains, but it does not grant that administrator permission to read, share, change, or delete the meeting.
The main side effects are:
- a new explicit share creates an in-app notification for the recipient;
- an access request and its approval or rejection create in-app and email notifications for the eligible current members;
- a manual visibility change schedules in-app and email notifications for the current internal meeting participants and owner, excluding the actor;
- deleting a meeting permanently removes the Infra One meeting and signals Contacts to remove its derived meeting log. It attempts email, but creates no in-app link, for the other current organization-member attendees and current owner. Neither the Contacts cleanup nor email result rolls back the deletion. Share-only viewers are not recipients, and the source meeting remains at the provider.
External attendees and people who have left the organization are excluded from those internal meeting-recipient sets.
Start using Conversations
Follow Review a meeting in Conversations for a read-only first pass. Continue with Manage meetings and provider connections before changing meeting access, deleting a meeting, or configuring Krisp or Granola.