Recordings & Transcripts

Is this feature for you?

Overview

Recordings & Transcripts gives users a searchable library of their Microsoft Teams meetings inside Unique. It has two halves, and both must be in place for the feature to work:

1. Capture — the Teams MCP Server, running with the knowledge-base integration enabled, receives a webhook from Microsoft Graph whenever a meeting transcript becomes available. It fetches the transcript (and the video recording, if one exists), creates a folder structure in the Unique knowledge base, applies participant-based access, and uploads both files.

2. Presentation — the Recordings area in Unique (reachable from the main navigation, at /chat/recording) lists everything that was captured. Users can filter the list, watch the recording with the transcript synchronised alongside it, read AI-generated reports, share a meeting with colleagues, and open a chat about it.

Because capture happens through Teams MCP, Teams MCP is a hard prerequisite — there is no other supported way to populate the Recordings area today.

Requirements

What users see

Recordings list

The Recordings entry in the main navigation opens a table of every captured meeting the user has access to:

• Filters — free-text search on the meeting title, plus filters for date, host, and participants

• Columns — title and duration, date, host, participants, and a per-row action menu

• Actions — Share to grant colleagues access, and Delete for users who hold knowledge-base write or admin permission

• Rows load progressively as the user scrolls

Recording detail

Selecting a meeting opens its detail view:

• Video playback when a recording was captured, with the transcript panel synchronised to the playhead

• Transcript with speaker labels, in-transcript search, and click-to-seek — available even when no video exists

• Meeting metadata — date, duration, and the full participant list

• Reports — AI-generated summaries produced from the transcript, each expandable, with a refresh action for reports that are still being generated

• Open chat — starts a Unique chat in the configured space with the meeting as context

Sharing and access

Access is derived from the meeting itself: the organiser receives read and write access, participants receive read access, and users are matched to Unique accounts by email or username. Anyone with access can additionally share a meeting from the list, granting Can view, Can edit, or Can manage to individual users or groups, or copy a direct link.

What is stored

Everything is written beneath a single dedicated root scope, one folder per meeting and one child scope per session, so a recurring series collapses into one folder with a child per occurrence. Content is attributed to the Microsoft Teams source, and the transcript and its recording are linked by a shared correlation id. See the Technical Manual for the exact layout and metadata.

User workflow

1. Connect (one-time) — the user connects their Microsoft account to the Teams MCP Server and grants consent

2. Enable ingestion (one-time) — the user calls the start_kb_integration tool, or the operator enables UNIQUE_AUTO_START_INGESTION so that connecting is enough

3. Attend meetings (ongoing) — any meeting with transcription enabled is captured automatically once the transcript becomes available; there is normally a delay of several minutes after the meeting ends

4. Use the library (ongoing) — the meeting appears in the Recordings area, is searchable by Unique AI, and remains available even if the user later disconnects their Microsoft account

To capture a meeting that predates the integration, or one that was missed, the user can ingest it explicitly with the ingest_meeting tool — see Ingestion tools.

Limitations and constraints

Capture is forward-only

Meetings are captured from the moment a user enables ingestion. There is no backfill of earlier meetings and no delta sync to catch up on missed ones, because Microsoft Graph does not offer either capability to applications using delegated permissions. If a webhook subscription lapses, transcripts produced during the gap are lost permanently and must be pulled in individually with ingest_meeting. The full reasoning is in Microsoft Graph constraints.

Not supported

• Real-time transcription — only completed transcripts are processed, not live captions

• Selective capture — every meeting with transcription enabled is captured; there is no filter by organiser, meeting type, or title

• Transcript formats other than VTT — meetings whose transcript is not available as VTT are skipped silently

• Very large recordings — there is no application-level size limit, so a multi-hour recording may time out during download and be skipped; the transcript is still captured

• Sources other than Microsoft Teams — the Recordings area only shows content captured from Teams

• On-demand report generation from the UI — reports appear when the platform generates them; the user cannot trigger a new report from the Recordings area

Retention

Deleting a meeting from the Recordings area removes the transcript, the correlated recording, and its reports from the Unique knowledge base. Disabling ingestion with stop_kb_integration stops future capture but does not delete anything already captured. Note that Microsoft applies its own expiration policy to transcripts and recordings on the Teams side (Microsoft's default is 120 days), which is independent of what Unique stores.

Related Documentation

• Operator Manual — prerequisites, configuration, enablement checklist, and troubleshooting

• Technical Manual — architecture, ingestion pipeline, subscription lifecycle, tools, and data model

• FAQ — frequently asked questions

Teams MCP

• Teams MCP — the MCP server that captures transcripts, and its chat and channel messaging tools

• Teams MCP - Operator Manual — deploying and operating the server

• Teams MCP - Authentication — Entra ID app registration and admin consent

• Teams MCP - Permissions — Microsoft Graph permissions with least-privilege justification

Standard References

• Microsoft Graph API - Microsoft Graph documentation

• Microsoft Graph Change Notifications - Webhook subscription model

• Limits and specifications for Microsoft Teams - Meeting and transcript expiration

• WebVTT - The transcript format