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

# How meetings get in

> Three ways for MeetingKit to learn about your users’ meetings, and the pair we recommend.

MeetingKit records a meeting once it knows about it. There are three ways to tell it, and
you don't need all of them.

**We recommend connecting calendars, plus a "Send bot to meeting" button.** Your users
connect their calendar once, and every meeting on it follows their recording choices. The
button covers the calls that are on no calendar.

<Frame>
  <img src="https://mintcdn.com/meeting-kit/t6WSr7K7AaKoVL2b/images/diagrams/meetings-get-in.svg?fit=max&auto=format&n=t6WSr7K7AaKoVL2b&q=85&s=66a17bc8eb8e50e0689860939d623176" alt="Six ways in, one card each: 1 connect calendars on MeetingKit's consent screen (POST /calendar_connect_links); 2 the same connect link under your brand, coming soon; 3 push calendar events you already sync (POST /calendar_events); 4 a directory connection for Google Workspace or Microsoft 365, coming soon; 5 send bots to a meeting link (POST /bots); 6 invite by email to bot@meetingkit.com, coming soon." width="680" height="551" data-path="images/diagrams/meetings-get-in.svg" />
</Frame>

| Way in | You build | MeetingKit handles | Pick it when |
| - | - | - | - |
| [Connect calendars](/meetingkit/calendar-connection) | A connect button and a settings screen. | The calendar sync, reschedules and cancellations, which meetings to record. | Your product doesn't sync calendars. **Recommended.** |
| [Push calendar events](/meetingkit/calendar-sync) | Forward each event your calendar sync receives. | Reschedules and cancellations, which meetings to record. | Your product already syncs your users' calendars. |
| [Send bots](/meetingkit/send-bot#from-a-button), from a button | A "Send bot to meeting" button. | Joining the call now. | Always, next to either calendar source, for ad-hoc calls. |
| [Send bots](/meetingkit/send-bot#from-your-backend), from your backend | A bot per meeting, kept in step with your calendar. | Joining at the time you set. | Your backend already decides which meetings to record. |

Use one calendar source per workspace: connected calendars or pushed events, not both. A
call that arrives from both becomes two meetings, and only one of them gets the recording.

Whichever way a meeting gets in, it is the same [meeting](/meetingkit/meetings), with the
same results.

## Coming soon

* **Connect calendars under your brand.** The same [connect link](/meetingkit/calendar-connection),
  through your own Google or Microsoft app: the consent screen shows your product's name
  instead of MeetingKit's. You register a calendar-only app once and give MeetingKit its
  credentials; MeetingKit still runs the consent, the tokens and the sync.
* **Directory connection, Google and Microsoft.** A customer's admin connects the whole
  company in one step: a Google Workspace domain or a Microsoft 365 tenant. MeetingKit reads
  the directory and creates a member and a calendar connection for each person, with no
  click from each user, and keeps up with joiners and leavers.
* **Invite by email.** A user adds the notetaker's address, such as `bot@meetingkit.com`, to
  a meeting invite, and it joins. No calendar to connect.