Notion · Notion AI

AI Meeting Notes

Notion AI feature that captures meeting audio, transcribes it and generates a structured summary including key points and action items inside an AI Meeting Notes block.

Recorded characteristics

Function
Notion documents that AI Meeting Notes "takes detailed meeting notes for you", transcribing the meeting and identifying key points and action items. A user inserts an AI Meeting Notes block (/meet, the Meetings tab, Home upcoming-events tile, or Notion Calendar) and selects Start transcribing; selecting Stop automatically starts generation of an AI summary, and at least one minute of recorded audio is required for a summary to be generated. Transcription starts a new line when the speaker changes, and on the desktop app speakers can be labelled, with participant names available when the note is linked to a calendar event. Summaries contain citations back to specific transcript lines. Summary structure can be set through built-in or custom Instructions, and an existing summary can be regenerated with Retry summary. Existing audio files (AAC, M4A, MP3, WAV) can be uploaded to a Meeting Notes block for transcription and summarisation. Notion documents that action items are identified within the generated notes; it does not document the feature executing those action items.
Data access
Documented inputs are meeting audio and content the user places in the block. In the Notion desktop app both system audio and microphone audio are captured; in the browser only microphone input is transcribed and system audio is not captured; on mobile only what the phone microphone picks up is transcribed. Notion states that system audio and screen recording permissions are required to transcribe other participants when headphones are used. Notes or agenda items typed under Notes before the meeting are taken into consideration when the summary is generated, and selected Instructions (including a custom instructions page) shape the summary. The meeting transcript itself is the input to summary, action-item and insight generation. Uploaded audio files (AAC, M4A, MP3, WAV) are also processed. Where a note is created from or linked to a Notion Calendar event, event context is used: the meeting page carries the event name, date and time, and calendar participant information can be used for speaker labelling. This is event-scoped context; the documentation does not establish access to the user's wider calendar, and does not establish that this capability reads wider Notion workspace content.
Actions
Generative only
External actions
Unknown
Human confirmation
Not established
Permission basis
Not established
Administrative control
Notion documents workspace-owner controls in Settings -> Notion AI: a Workspace availability toggle, which Notion states is how AI Meeting Notes is turned off for the workspace (and an AI Meeting Notes toggle referenced where the /meet command is unavailable); an "Enforce consent for all workspace members" setting (introduced 12 March 2026) that makes the audio consent message play automatically at the start of each transcription for all users; and a "Store audio locally" opt-in, which Notion states is turned off by default for all plans. Enterprise Plan workspace owners can set an Automatic transcript deletion schedule, which also deletes the associated locally stored audio and does not delete transcripts on legally held pages. Notion's AI settings overview lists AI Meeting Notes settings covering audio storage, transcript deletion and more. Distinct from these workspace controls, individual users control auto-play of the consent message for themselves where it is not enforced, a default meetings database, automatic sharing of notes created from a Notion Calendar event with workspace-member participants, deletion of an individual transcript or locally stored audio, and hiding the Meetings tab.
Default state
Not established
Availability
Notion states AI Meeting Notes requires the Business or Enterprise plan, and is also available for eligible mobile subscriptions where Notion AI is included. It is available in the Notion app, browser and mobile app, with the desktop app required for system-audio capture; desktop app version 4.7.0 or higher, macOS 13 or later, and the latest Windows version are stated requirements. Notion's AI FAQ lists the feature as AI Meeting Notes (beta), and a daily usage limit of 10 hours per user is documented. Supported languages are English, Chinese, Spanish, French, German, Japanese, Korean, Portuguese, Russian, Thai, Vietnamese, Danish, Finnish, Norwegian, Dutch and Swedish; speaker labelling is English only. The Meetings sidebar tab is documented as still rolling out. The feature is not supported offline.
Licensing
Notion states that use requires the Business or Enterprise plan, or an eligible mobile subscription where Notion AI is included. No further pricing detail for this capability is established by the reviewed documentation.
External model or provider
Notion states that AI Meeting Notes engages sub-processors - OpenAI, Anthropic, Fireworks, Baseten Labs, Inc., X.AI LLC and AssemblyAI Inc. - to record the meeting, process the audio file into a transcription and produce insights such as a meeting summary, action items and call participants. This is the documented set of providers engaged by the feature; Notion does not state which provider or model performs any specific step, and it must not be read as every listed provider processing every meeting. Notion also documents that in the app or browser audio is sent directly to sub-processors for real-time transcription, that sub-processors do not store audio, and that on mobile the audio file is uploaded to Notion's servers before being sent to sub-processors.
Limitations and uncertainty
ESTABLISHED by current Notion documentation: the capability transcribes meeting audio, identifies key points and action items, and generates an AI summary that can draw on both the transcript and notes the user typed in the block; documented inputs are microphone audio, system audio on the desktop app, uploaded audio files, the transcript, in-block notes and event-scoped Notion Calendar context used for speaker labelling; meeting notes inherit the permissions of the page they are saved on, are private to the creator by default, and must be shared manually unless the optional calendar-participant auto-share setting is used; workspace owners can turn the feature off, enforce the consent message workspace-wide (12 March 2026 release), control local audio storage (off by default) and, on Enterprise, set automatic transcript deletion; availability requires a Business or Enterprise plan or an eligible mobile subscription; and the sub-processors engaged for recording, transcription and insight generation are documented. NOT ESTABLISHED: the capability generates transcripts, summaries and lists of action items, and Notion does not document it executing any action arising from those items - identification of an action item must not be read as execution, and no external operational action is documented (creating a meeting-note page and reading calendar-event context do not establish one). Human confirmation of an AI-selected operational action is not established: the user selects Start transcribing, which Notion treats as the recorder confirming participant consent, but that is initiation of recording rather than approval of an action. Runtime authority is not established: the documented page-permission inheritance governs who can access the stored meeting note, not the identity or permissions under which transcription and summarisation execute, and other documented permissions concern device audio/screen-recording access and workspace availability settings. The operational default state of AI Meeting Notes itself for an eligible workspace is not stated; the workspace owner's ability to turn it off, and the separate "Store audio locally" setting being off by default, do not establish it. Which individual sub-processor or model handles any particular meeting or step is not stated. Retention of derived data beyond documented transcript/audio handling and workspace data-retention settings is not established. Documented operational limits: browser capture is microphone-only and misses conferencing audio when headphones are used; mobile captures only phone-microphone audio; virtual desktop (VDI) environments capture only microphone audio unless Notion's local plugin is installed; at least one minute of recorded audio is required for a summary; speaker labelling is unreliable for group or in-person meetings and is English only; transcripts can contain errors or made-up words with little or poor-quality audio; MOV, MP4 and Loom files are not supported for upload; audio handling is documented (sub-processors do not store audio; audio uploaded after failed real-time processing is retained up to 3 days; local copies are deleted after successful processing or within 24 hours). Consent for recording is documented as the user's responsibility and Notion states its guidance is not legal advice.

Evidence