Internal: Meeting Notes (docs/specs/MEETING_NOTES.md), still behind MeetingNotesPolicy::MEMBERS_ENABLED = false and so for site administrators only. API v1 has the rest of the area for the Magpie app and the Mac app: list and search meeting notes, upcoming meetings, make one from nothing or for a booking, Calendar event, Google event or scheduled call, read one, change its details and texts with a stale check per text, people, the chatbot text, Import JSON, Add to To-dos, Move to Trash and Meeting Notes settings, each with the website's checks (docs/API_V1.md). Connected apps get get_meeting_note_content, which the assistant shares and which never returns the transcript, and read_meeting_note_transcript, a tool for connected apps only that the assistant cannot reach, whose output is not kept (docs/MCP_SERVER.md); the consent page says the app can read transcripts, and only a connection made past that line gets the tool (an earlier one connects again for it). get_meeting_note_content lists the linked To-dos only for an app granted To-dos. Someone a meeting note is shared with at once, a member of its team or a guest, is emailed a link to it in their own language. On a meeting note, the People band's Name field suggests the team's contacts as it is typed, and a contact picked is linked even when it has no email address. See docs/plans/MEETING_NOTES_HANDOFF.md.
Meeting Notes in API v1 and for connected apps, and a sharing email
Internal: Meeting Notes, still for site administrators only, now has the API v1 routes the apps need, read tools for connected apps, an email to someone a meeting note is shared with, and contacts to pick by name in People.