> For the complete documentation index, see [llms.txt](https://docs.cogram.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cogram.com/meetings/one-notetaker-per-meeting.md).

# One notetaker per meeting

One Cogram Notetaker per call for the whole organization, with a copy of the notes for everyone who invited it.

With one notetaker per meeting, a call gets one Cogram Notetaker for your whole organization, however many colleagues invite it. Everyone who invited it still gets the meeting in their own **My Workspace**, with their own copy of the notes.

There are three ways to invite the notetaker: click **Attend** in the Cogram calendar, forward the meeting invite to Cogram, or paste the meeting link into Cogram. Any of the three gets you your own copy of the notes.

Being on the calendar invite for the meeting is not one of them. That is the difference that decides who gets a copy.

## Turning it on (Admins)

Org Admins and Owners turn it on under [Organization Settings > Meetings](https://app.cogram.com/dashboard/settings/admin/meetings): **Allow only one notetaker per meeting organization-wide**.

Meetings your team already booked keep their notetakers for now. Cogram settles each one shortly before the call starts: it keeps the notetaker invited first and stands the others down, and the colleagues whose notetaker stood down get a copy of the notes instead. Nobody has to click Attend again.

It also changes who gets notes. One recording stands for the whole organization, so everyone who invited the notetaker gets their own copy instead of only the colleague who invited it first. See [After the call](#after-the-call).

### The notetaker's name

While the setting is on, a call that several colleagues invited the notetaker to gets the notetaker name set under **Notetaker settings** on the same page ("Cogram Notetaker" unless you changed it). A call nobody else invited it to keeps the name the person who did would get anyway, from their personal settings, their group's, or your organization's if you lock it.

Your organization's name can still use the `{{first name}}` and `{{last name}}` placeholders. On a call nobody else invited the notetaker to, they fill in with the person whose call it is. On a shared call Cogram leaves them out, so no colleague's name is carried into another's meeting. Cogram never changes the name you saved.

## What members see

### Before the call

* In the [calendar](https://app.cogram.com/dashboard/meetings/schedule), **Attend** turns on as usual. If a colleague already invited the notetaker, a line under the toggle says so and that your copy of the notes will follow.
* Forwarding the invite to Cogram works the same way. The reply names the colleague who already invited the notetaker instead of scheduling a second one.
* If you paste a meeting link into Cogram while the notetaker is already in that call, Cogram tells you who invited it and that your copy will follow. No second notetaker joins.
* When a colleague invited the notetaker to the same call before you, your own meeting leaves your list shortly before the call starts, and you become an attendee of theirs. Your copy of the notes arrives after the meeting as usual.

### In the call

One notetaker joins. On a call several colleagues invited it to, it uses the name set under Notetaker settings.

If you clicked **Attend** and a colleague already invited the notetaker, the meeting shows on **All meetings** until your own notes arrive. It does not show under **Owned by me** or **Shared with me**.

* The row shows the title, the time, and the same status as the meeting page. **Project** and **Owner** show a dash, because they are the sponsor's and not yours.
* **Leave** is on that row, and on the calendar event, while the notetaker is joining, waiting, live, or paused. Cogram asks you to confirm. It is not there while the notetaker is restarting, leaving, or after the meeting has failed.
* Leaving while the notetaker is in the call ends the recording for everyone. Opening the meeting address then shows **Stopped by** and the name of the person who asked it to leave. The row itself does not name them.
* Leaving before the notetaker has joined removes the row, because nothing was recorded. An address you already have open says: "This meeting wasn't recorded." Your colleagues are told too. See [If the notetaker is stopped before it joins](#if-the-notetaker-is-stopped-before-it-joins).
* The title is not a link. While the call is going, hovering the title or clicking the row says: "You'll get your own notes when the meeting ends." Once the call has ended and the notes are still being prepared, it says: "Your notes are on the way."
* Opening the meeting address shows the meeting's name and **Your notes are on the way**. While the call is going, the page also says the notes arrive when the meeting ends. The page updates when the call ends.
* If the notetaker fails, the row stays. Hovering it, clicking it, or opening the address says: "This meeting wasn't recorded." Cogram also emails you the reason it could not take notes, whether or not the colleague who invited it has failure emails switched on.

When your notes are ready, that row is replaced by your own meeting.

### After the call

* Everyone who invited the notetaker gets the meeting in their own **My Workspace**, with the transcript, summary, and action items, and their own post-meeting email. You can edit, file, or delete your copy without affecting anyone else's.
* Being on the calendar invite for the meeting does not count. Somebody who was invited to the event but never invited the notetaker gets no copy of their own.
* Whether those invitees see the notes at all is up to **Minutes sharing**, the same as on any other meeting. With it on, invitees who are members of your organization get a read-only link instead of a copy.
* A project keeps one record of a meeting. If a colleague already filed it to a project, your copy stays in My Workspace and shows a folder glyph next to the project picker. Hover it to see who filed the meeting and where. If you try to file your copy there too, Cogram tells you who already filed it, and Cogram suggests no project of its own for that copy.

Nobody outside your organization is given a copy, and inside it Cogram leaves out anyone who switched **Attend** off for that meeting or already has their own recording of the same call.

### If the meeting is deleted before the notes arrive

This covers a colleague deleting the call from their meetings list or from a project's assets, and a canceled calendar event.

* Colleagues who clicked **Attend** in the calendar get a new notetaker automatically, as long as the meeting started less than ten minutes ago. It joins the rest of the call.
* Everyone else gets an email with the way back, matching how they invited it: click **Attend** in the Cogram calendar, forward the invite to Cogram again, or paste the meeting link into Cogram again.

### If the notetaker is stopped before it joins

Leaving the call before the notetaker has joined stops it for the whole organization, because there is nothing recorded for anyone yet.

* Everyone else who invited it gets an email within a few minutes, saying the notetaker was stopped before it started recording.
* No way back is offered. Somebody has just asked Cogram to leave, and putting a notetaker straight back would undo that. If the meeting is still running and you do want notes, invite the notetaker again the way you did the first time.
* The person who stopped it is not emailed about their own action.
* Once that email has gone out, a meeting address a colleague still has open shows "403 - Meeting not found". The email is what carries the explanation.

## Next steps

* [Renaming your Notetaker](https://docs.cogram.com/meetings/renaming-your-notetaker.md)
* [Virtual meetings](https://docs.cogram.com/meetings/virtual-meetings.md)


---

# 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.cogram.com/meetings/one-notetaker-per-meeting.md?ask=<question>&goal=<user_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.
