> For the complete documentation index, see [llms.txt](https://docs.zero.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zero.inc/features/calendar.md). # Calendar Meetings synced from your connected Google or Outlook calendars (see [Calendar Settings](/settings/mailbox-settings/calendar-settings.md)) each get a page in Zero, where the prep, notes, transcript and follow-up for that call all sit together. There is no calendar entry in the sidebar. You arrive through the **Calendar** tab of the [Home](/features/home-view.md) sidebar, through a meeting link anywhere in the app (chat, a record's activity feed, a linked task), or through the [command menu](/getting-started/command-menu.md) once **Show calendar events** is on in its footer. The direct URL for a meeting is `//calendar/`. ## The meeting page Everything about a meeting collects on its own page. At the top you can set an emoji (default ☕), edit the name, see the date and time, and assign **meeting labels** (configured under **Settings → Workspace → Types & Labels**). Then four tabs: * **Meeting prep** — the AI-generated briefing for the meeting. Only shown for meetings with external participants. See [Meeting Prep](/features/home-view/meeting-prep.md). * **Meeting notes** — always there (see below). * **Transcript** — enabled once the meeting has a transcript (from Zero's recorder or a connected notetaker, see [Call Recorders](/settings/call-recorders.md)). Shows the recording player when a playback is available, and the transcript grouped by speaker with timestamps. * **Follow-up** — enabled once a follow-up draft or thread exists for the meeting. Shows the drafted follow-up email in a composer; after sending, it shows the sent email with a **"Follow-up sent by \"** banner. See [Generate Follow-up](/features/home-view/generate-follow-up.md). Link straight to a tab with `?tab=prep`, `?tab=notes`, `?tab=transcript` or `?tab=followup`. Without it the page opens on **Meeting notes** when notes exist, otherwise on **Meeting prep** for external meetings. While a recording is still processing you see the stage instead — **"Recording in progress..."**, **"Transcribing audio..."**, **"Generating notes with AI..."**. ### Meeting notes and tasks The **Meeting notes** tab holds both the notes — a rich-text editor with @-mentions, attachments and your workspace's note snippets — and the **Tasks** linked to the meeting, including action items pulled out of the transcript. **Add task** adds another. ### Details sidebar On the right: the time, **Location** and meeting link; **Participants**, with anyone lacking a contact record grouped under **Not in Zero**; **Deals** associated with the meeting's companies and contacts; and, after a transcribed meeting, **Speaker activity** — the share of talking time per speaker. The panel collapses on narrow windows; **Show details** / **Hide details** toggles it. ## Visibility The button in the top-right corner says whether the event is **Public** (the whole workspace) or **Private** (only associated users), and clicking it toggles — but only someone associated with the event can. Open a private event you are not part of and you get **"This calendar event is private."** with a nudge to ask someone who is. The default visibility for newly synced events is configured per calendar — see [Calendar Settings](/settings/mailbox-settings/calendar-settings.md#event-visibility). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.zero.inc/features/calendar.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.