Calendar
Back to the guide
Settings → Calendar
Connecting a calendar logs your meetings against the CRM records of the people who attended, so a record shows not only what was emailed but what was met about.
Connecting
Calendar access is granted on the same mailbox you connected under Settings → Email. If a provider is not offered, it has not been enabled on the server — an administrator matter rather than something you can change.
What it does
Each connected calendar is checked every five minutes.
When a meeting has finished, it is logged against the records of the people who were on it. Attendees are matched to contacts by email address, the same way email sync matches people, and a contact is created when there is not one already.
A meeting appears on a record as a note of kind Meeting, so it sits in the timeline alongside calls and notes rather than in a separate place. See Notes, calls and meetings.
Finished meetings are logged in batches, so a calendar with a large backlog fills in over several passes rather than all at once.
Meetings that did not happen
A meeting in the calendar is not proof a meeting took place. Cancellations that never left the diary, and calls nobody joined, would otherwise become a record of conversations that never occurred.
So a logged meeting can be marked as not having happened, which removes it from the record rather than leaving a misleading entry.
When access is removed
If calendar access is revoked at Google or Microsoft, syncing stops and the mailbox says so, asking you to reconnect. Reconnecting resumes it.
This is the same reconnect flow as email, because it is the same mailbox connection.
Privacy
Calendar data is never sent to an AI model. The privacy policy states this explicitly, and it is one of the commitments made to Google as part of app verification.
Jev reads emails and notes. It does not read your calendar.