> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.resemble.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.resemble.ai/_mcp/server.

# Meetings Control Center

The control center holds your personal settings. To open it, click **Edit Personal Settings** at the top of the Meetings page.

* On the **Protect every meeting** screen, use the **Edit personal settings** link instead.
* If the button reads **Edit Organization Settings**, pick **Personal** under **Calendar Scope** first.

![The top of the Meetings page with the Edit Personal Settings button highlighted](/_fern-img/b4b4f747760c952d1677bf60a59fc319dd328ff7fbec2a69920bda59930e4348.webp)

The sections below appear in this order, and each applies only to your own meetings.

## Autojoin Preferences

Pick which calendar meetings the bot joins under **When should the detection agent join your meetings?**

![The Autojoin Preferences menu open, showing its five options](/_fern-img/ce095b5c8e39496ab095798a9b98f5a5a2c9d31b2c2e3911f023598acef996ae.webp)

| Option                                                    | The bot joins                                                                   |
| --------------------------------------------------------- | ------------------------------------------------------------------------------- |
| **All meetings with a meeting link** (default)            | Every meeting with a Zoom, Microsoft Teams, or Google Meet link                 |
| **Only meetings inviting 'resemble-detect\@resemble.ai'** | Meetings with the bot on the invite, whoever added it                           |
| **Only meetings that I host**                             | Meetings you organize                                                           |
| **Only internal meetings**                                | Meetings where the organizer and every invitee use your calendar's email domain |
| **Only external meetings**                                | Meetings with at least one invitee or organizer from another domain             |

* **Hosted, internal, and external** follow your connected calendar's email, not your Resemble login.
* **Changing the option** re-checks your upcoming meetings, and you see **Applying to your upcoming meetings...** until it's done. Meetings that now match get the bot. Meetings that no longer match lose it.

> **Invite the bot to a specific meeting**
>
> Invite **resemble-detect\@resemble.ai** to an event on your connected calendar before it starts. The bot joins that meeting regardless of your autojoin option, as long as the event has a meeting link and, if the [Meeting Filter](#meeting-filter) is on, its title matches one of your keywords.

## Bot Name

Set the name the bot shows when it joins your meetings. Edit **Display name** (up to 100 characters, and it can't be blank), then click **Save**. The default is **Resemble's Deepfake Detector**.

![The Bot Name section with the Display name field](/_fern-img/fc33eeff40d17c75a4d51e753a9c0ba9620e102f79ef95932ef5dcede96dda9c.webp)

## Bot Leave Behaviour

Choose when the bot leaves a meeting on its own. Enter both values in seconds, then click **Save**.

![The Bot Leave Behaviour section with the Everyone left timeout and Waiting room timeout fields](/_fern-img/852ef6ec408279eef87dbc95c3bf1419490b25667022a9b4374e658813ce877c.webp)

| Setting                   | What it does                                                                  | Default         |
| ------------------------- | ----------------------------------------------------------------------------- | --------------- |
| **Everyone left timeout** | How long the bot stays after everyone else leaves. Minimum 1 s.               | 2 s             |
| **Waiting room timeout**  | How long the bot waits in a waiting room or lobby to be let in. Minimum 30 s. | 1200 s (20 min) |

> **Note**
>
> The bot also leaves if no one else joins within 10 minutes of the bot joining.

## Calendar Integrations

This section shows **Connected** or **Not connected**. Use it to connect, switch, or disconnect your calendar.

![The Calendar Integrations section showing a Connected badge](/_fern-img/79049a037453c9dc30549bde1a5d61fe24489eb33e416a019b1b46378034be44.webp)

* **Connect:** click **Connect Google Calendar** or **Connect Microsoft Outlook** and sign in, as in [Connect Your Calendar](/detect/meetings/personal-calendar/connect). This uses your saved autojoin option.
* **Switch calendars:** click the other provider's button, confirm **Yes, switch**, and sign in to the new calendar.
* **Disconnect:** click **Disconnect**.

> **Switching or disconnecting removes upcoming meetings**
>
> When you switch or disconnect, your current calendar's upcoming meetings and scheduled bots are removed. Past meetings and their results are kept.

## Meeting Filter

Limit the bot to calendar meetings whose titles contain your keywords. Bots you add with **Start meeting** aren't filtered.

1. In **Meeting Filter**, turn the switch on. The badge changes from **Disabled** to **Active**.
2. Enter keywords in **Keywords (comma-separated)**, for example `Interview, Board Meeting`.
3. Click **Save Changes**, which appears once you change something.

![The Meeting Filter section turned on with the keywords Interview and Board Meeting](/_fern-img/5d31eb21af0e946b2d9ab210d81cd9660dc90882790fb5bf1869a8a43334a689.webp)

### How matching works

* Separate keywords with commas.
* Matching ignores case and finds a keyword anywhere in the title, so `view` matches "Interview". A title with any one keyword matches.
* With the switch on and no keywords, every meeting matches.
* A meeting needs to pass both the filter and your autojoin option.
* Saving re-checks your upcoming calendar meetings right away. Meetings that now match get the bot. Meetings that no longer match lose it.

## Team Notifications

Send an alert email to the addresses you list when a call ends with a flagged participant. This needs a plan that includes security notifications. Otherwise the field is disabled and you see **Security notifications are not available on your current plan.**

1. In **Team Notifications**, enter up to 10 addresses in **Notification emails**, separated by commas or new lines.
2. Click **Save**.

![The Team Notifications section with the Notification emails field](/_fern-img/d4f66db6c30aad59617208ded51751e042ba3c3359973465be8831305e7074a6.webp)

* Alerts are sent once per meeting, after the call ends. They come from **Meeting Deepfake Detection Alert** at security-alerts\@resemble.ai.
* If any address is invalid or there are more than 10, nothing is saved and you see **Failed to update notification emails**.

## In-Meeting Chat Notifications

When the bot flags someone, it posts this message in the meeting chat:

> 🚨 DEEPFAKE DETECTED: `<name>` is using AI-generated content

Turn on **Suppress chat notifications** to stop these posts. Detection keeps running either way. The setting is off by default, so posts are sent.

![The In-Meeting Chat Notifications section with the Suppress chat notifications switch turned off](/_fern-img/c4a8e5b53febb3de2953480ed637b3a8f9d469cb0182dabc5847a0350d43b942.webp)