Meeting Configuration
Which meetings Meeting Automation includes, and how users control that.
Scope model
Meeting Automation is opt-in per user. A user connects their Google account, then chooses which meetings are in scope. Meetings outside that scope are never read.
Choosing meetings
Recommended starting scope:
- External customer meetings where follow-up actions are common.
- Recurring account reviews.
- Meetings where Gemini notes are already being generated.
Meetings usually excluded:
- One-to-one internal HR or performance conversations.
- Personal calendar entries.
- Meetings with no notes produced.
Requirements per meeting
| Requirement | Why |
|---|---|
| Meeting is on the connected Google account's calendar | The integration reads only authorized calendars |
| Notes were produced for the meeting | Action items are extracted from notes, not audio |
| Meeting falls inside the configured lookback window | The scheduled job only processes recent meetings |
Changing scope later
Users can change their meeting selection at any time from the app. Changing scope does not delete previously created Salesforce Tasks; it only affects future processing.
See the End-User Guide for the user-facing steps.
Was this helpful?
Last updated 1 month ago