> ## Documentation Index
> Fetch the complete documentation index at: https://docs.granola.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Transcribing policies

> Set workspace policies that ask members to confirm, warn them, or prevent transcription in certain meetings.

> [!NOTE]
>
> Transcribing policies are available on the **Enterprise** plan only.

Enterprise workspace admins can use transcribing policies to decide when members can transcribe meetings. Policies apply to everyone in the workspace.

## Create or change a policy

1. In the web admin portal, select the workspace you want to manage, then open [**Settings > Transparency > Transcribing policies**](https://admin.granola.ai).
2. Select **Add new transcribing policy**, or **Edit** on an existing policy.
3. Choose **When** the policy applies, then what happens under **Then**.
4. Optionally [change the message](#customize-the-message) under **Message members see**.
5. Select **See a preview** to see the message and buttons members will see, then **Back to setup** to keep editing. Preview buttons do not start transcription.
6. Select **Apply**.
7. Select **Apply changes** to save the policy for everyone in the workspace, or **Back** to return to the policy and keep editing.

## Choose what happens

| Action | What members experience |
| - | - |
| Ask for confirmation | Members must confirm that the meeting follows your workspace's policies before transcribing. |
| Warn, but allow an override | Members see a warning that your policy says not to transcribe. They can override it and continue. |
| Prevent transcription | Members cannot transcribe matching meetings or override this policy. |

If several policies match, a policy that prevents transcription takes priority. Other matching policies can appear together in a single confirmation or warning. A preview shows one policy on its own.

![Granola prevents transcription of an Investment Committee meeting and shows the workspace's custom policy message.](https://mintcdn.com/granola-c3940166/hpfQ9Pj_RELH1eHH/assets/screenshots/transcribing-policy-prevent-framed.png?fit=max\&auto=format\&n=hpfQ9Pj_RELH1eHH\&q=85\&s=9782233558e109ff45129a1aa18d5add)

## Choose when a policy applies

| Condition | How it matches |
| - | - |
| Someone outside your company is invited | A calendar invitee has an email domain outside your workspace's internal domains. |
| Only people from your company are invited | All eligible invitees are internal, with at least one person other than the member taking notes. |
| Someone from a specific domain is invited | An invitee's email domain matches one of the domains you enter. Enter one per line, such as `example.com`. |
| Specific people are invited | An invitee's email matches one of the addresses you enter. Enter one per line. The member taking notes does not trigger their own policy. |
| Someone in a workspace group is invited | An invitee belongs to one of the workspace groups you select. |
| The meeting is in person | Granola detects no active meeting app, even if the invite has a conferencing link. This can include ad hoc notes. |
| The Zoom meeting is end-to-end encrypted | Zoom shows the meeting as end-to-end encrypted. If this is detected after transcription starts, transcription stops. |
| The meeting title contains certain words The meeting description contains certain words | The title or description contains any word or phrase you enter, anywhere in the text. Matching is not case-sensitive. Enter one phrase per line. |

Your company's internal domains include the workspace domain, any additional internal domains registered for it, and domains approved for link sharing. Invitees from any of these domains count as internal. Policies about who is invited ignore declined invitees, room resources, known bots and the member taking notes.

If a note isn't attached to a calendar event, calendar-based policies can still match an invited meeting currently in progress. Members see wording explaining that the match came from their calendar.

### Limitations of people and group policies

**Policies about who is invited use the calendar invite, which may differ from who actually joins a call. They are not a live attendance check.** The in-person policy is the exception: it checks for an active meeting app instead of the invite.

Policies for **specific people** and **a workspace group** can miss meetings in two common situations, described below. We're working on improving both. If you're planning to use these policies, [contact us](mailto:hey@granola.so?subject=Transcribing%20policies%20setup) to discuss your needs and we'll help you set them up for your organization.

#### People invited through a mailing list

A specific people policy matches the email addresses on the invite. If someone is invited through a mailing list or group address, such as `team@example.com` or `leadership@example.com`, their own address isn't on the invite. So if you add `alex@example.com` to a policy, it matches when Alex is invited directly, but may not match when only `leadership@example.com` is invited.

To cover meetings sent to a list, add the list's address to the policy as well. The policy then applies to every meeting that list is invited to.

#### Groups that only exist in your identity provider

A group policy matches people in the Granola [user groups](https://docs.granola.ai/help-center/sharing/user-groups.md) you select. Granola only knows about groups in your workspace, either created under **Members** or synced from your identity provider with [directory sync (SCIM)](https://docs.granola.ai/help-center/sso-setup-guide.md#set-up-directory-sync-scim). It can't see groups that exist only in your identity provider or HR system, such as a Legal team in your org chart.

A group policy also only matches people who are members of your Granola workspace. If you want to block meetings with people who don't use Granola, such as your whole Legal team:

* Add their email addresses to a **specific people** policy instead, along with any mailing lists they use.
* Or add them to your workspace and to the group, for example by syncing the group with directory sync. Each person then takes a seat in your workspace.

## Customize the message

The message box starts with Granola's default wording for the condition and action you chose. Edit it to write your own, up to **515 characters** including Markdown characters, or clear it to go back to the default. The message supports:

* `**bold**` and `*italic*`
* `[link text](https://example.com)` and automatically linked plain URLs
* Bullet lists using `- ` and numbered lists using `1. `

Headings, images and HTML are not supported. Select **See a preview** to check how the message looks to members.

To link to your company's policy, include a Markdown link in your custom message, such as `[Company policy](https://example.com/policy)`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.