> 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/settings/invitee-domain-lists.md).

# Invitee Domain Lists

Cogram can be configured to only join (or never join) meetings that include participants from specific email domains. This is useful for enforcing privacy boundaries, such as preventing Cogram from recording meetings with external parties.

These settings are under [Account Settings > Meetings](https://app.cogram.com/dashboard/settings/account-settings/meetings).

## Allow List

When an allow list is set, Cogram will only join meetings where all participants are from one of the listed domains. Meetings that include participants outside the listed domains will not be attended.

Leave the allow list empty to place no domain restrictions on who Cogram can join meetings with.

## Block List

When a block list is set, Cogram will not join any meeting that includes a participant from one of the listed domains, even if you have scheduled it to attend.

## Setting defaults for your organization (Admins)

Org Admins and Owners can set and lock domain lists for all members under [Organization Settings > Meetings](https://app.cogram.com/dashboard/settings/admin/meetings). This is useful for enforcing a consistent privacy policy across the organization.

| State        | What the end user sees                                                     |
| ------------ | -------------------------------------------------------------------------- |
| **Unlocked** | The org default is pre-filled, but the user can add or remove domains.     |
| **Locked**   | The field is grayed out with a lock icon. The user cannot modify the list. |

> **Note**: If your organization has locked these settings, you will not be able to edit the domain lists. Contact your Org Admin if you need them changed.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cogram.com/settings/invitee-domain-lists.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.