How Lea uses Google Calendar and Outlook

Last updated: August 13, 2026

Lea can use Google Calendar and Microsoft Outlook / Microsoft 365 calendar integrations to support real-time scheduling workflows. Once connected, Lea can check availability, suggest suitable meeting times, create calendar events, send invitations, and cancel meetings that were originally created through Teamspective.

This article explains what Lea uses calendar access for, what data is read, what actions Lea can perform, how technical administrators can configure the integrations, and how to troubleshoot common setup issues.

What Lea can do with calendar integrations

With a supported calendar integration connected, Lea can:

  • Check participant availability

  • Find free and busy time slots

  • Create calendar events on behalf of the organizer

  • Add attendees to meeting invitations

  • Include meeting details such as title, description, and time

  • Cancel meetings that Lea previously created through Teamspective

What calendar data Lea reads

Lea reads only the calendar data needed to support scheduling workflows:

  • Participant identity information, such as name and email address

  • Calendar availability and busy time

  • Event timing details

  • Attendee lists and response status when needed to manage a meeting

Lea does not take over users’ calendars or modify arbitrary existing meetings. Calendar write actions are limited to meetings created through Teamspective.

Prerequisites

Before setting up a calendar integration for Lea, make sure you have:

  • Administrator access to your Google Workspace or Microsoft 365 tenant

  • Permission to grant tenant-wide or domain-wide calendar access

  • Approval from your internal IT/security team, if required

  • A clear decision on whether Lea should only check availability or also create and cancel meetings

If Lea should create and cancel meetings, the integration must include write permissions. If write permissions are not granted, Lea can still be limited to availability lookup depending on the configured integration.

Google Calendar setup

Google Calendar is configured at the Google Workspace domain level. Teamspective uses a Google service account with Domain-Wide Delegation to access calendar functionality for scheduling.

Google requirements

  • Google Workspace administrator access

  • A Google Cloud project

  • A Google service account

  • Domain-Wide Delegation enabled for the service account

  • A Google Workspace super admin email for configuration

Google APIs used by Lea

  • Google Calendar API for availability lookup, event creation, and event cancellation

  • Google Admin SDK / Directory API for user identity lookup

Google scopes

For calendar and identity access, grant the required read scopes:

  • https://www.googleapis.com/auth/admin.directory.user.readonly

  • https://www.googleapis.com/auth/calendar.readonly

  • https://www.googleapis.com/auth/calendar.events.readonly

To allow Lea to create and cancel events, also grant:

  • https://www.googleapis.com/auth/calendar.events

Google setup steps

  1. Create or select a Google Cloud project.

  2. Enable the Google Calendar API.

  3. Enable the Admin SDK / Directory API.

  4. Create a service account.

  5. Enable Domain-Wide Delegation for the service account.

  6. In Google Workspace Admin, authorize the service account client ID for the required OAuth scopes.

  7. Provide the configured service account credentials and super admin email in Teamspective.

Google behavior notes

  • Availability checks use Google Calendar free/busy data.

  • Lea creates events in the organizer’s primary calendar.

  • If write access is enabled, Lea can send invitations and updates to attendees.

  • Lea can cancel meetings that were created through Teamspective.

Outlook / Microsoft 365 setup

Microsoft 365 calendar integration is configured at the tenant level using Microsoft Graph and admin consent. Teamspective uses application-level access for scheduling operations.

Microsoft requirements

  • Microsoft 365 administrator access

  • Microsoft Entra / Azure administrator permission to grant tenant-wide admin consent

  • Permission to grant Microsoft Graph application permissions

Microsoft Graph APIs used by Lea

  • getSchedule for availability lookup

  • Calendar event creation in the organizer’s calendar

  • Calendar event cancellation for meetings created through Teamspective

  • User lookup for participant identity and organizer resolution

Microsoft Graph permissions

For basic calendar and identity access, grant:

  • Calendars.ReadBasic.All

  • User.ReadBasic.All

To allow Lea to create and cancel meetings, also grant:

  • Calendars.ReadWrite

Microsoft setup steps

  1. Start the Microsoft calendar connection flow in Teamspective.

  2. Sign in with a Microsoft 365 tenant admin account.

  3. Review the requested Microsoft Graph application permissions.

  4. Grant tenant-wide admin consent.

  5. Confirm in Teamspective that the integration is connected successfully.

  6. Ensure Calendars.ReadWrite is granted if Lea should create and cancel meetings.

Microsoft behavior notes

  • Availability checks use Microsoft Graph scheduling APIs.

  • Lea creates meetings in the organizer’s calendar.

  • Meetings created through Microsoft 365 are created as online Teams meetings.

  • Lea can cancel meetings that were previously created through Teamspective.

Important limitations

  • Lea can only cancel meetings that were created through Teamspective.

  • Lea does not modify arbitrary existing meetings already present in a user’s calendar.

  • Calendar write actions require write permissions to be granted during setup.

  • If write permissions are not granted, meeting creation and cancellation will not be available.

Troubleshooting

Lea cannot find availability

  • Confirm the calendar integration is connected in Teamspective.

  • Verify that the relevant users exist in Google Workspace or Microsoft 365.

  • Check that read permissions were granted successfully.

  • For Google, confirm Domain-Wide Delegation is enabled and the service account client ID has the correct scopes.

  • For Microsoft, confirm tenant-wide admin consent was granted for the required Graph permissions.

Lea cannot create meetings

  • Confirm that calendar write permissions are enabled.

  • For Google, verify that https://www.googleapis.com/auth/calendar.events has been granted.

  • For Microsoft, verify that Calendars.ReadWrite has been granted.

  • Confirm the organizer account is active and has a primary calendar.

Lea cannot cancel a meeting

  • Confirm that the meeting was originally created through Teamspective.

  • Confirm that write permissions are still active.

  • Check whether the meeting was deleted, moved, or modified outside Teamspective.

Microsoft admin consent fails

  • Make sure the signed-in user has permission to grant tenant-wide admin consent.

  • Confirm that your organization allows admin consent for enterprise applications.

  • Review any conditional access policies that may block the consent flow.

Google authorization fails

  • Confirm that the service account has Domain-Wide Delegation enabled.

  • Verify that the correct service account client ID was authorized in Google Workspace Admin.

  • Check that all required OAuth scopes were added exactly as provided.

  • Confirm the configured admin email belongs to an active Google Workspace admin user.

Summary

Calendar integrations allow Lea to support scheduling workflows by checking availability, creating meetings, inviting attendees, and canceling meetings created through Teamspective. Google Calendar uses a service account with Domain-Wide Delegation, while Microsoft 365 uses Microsoft Graph application permissions with tenant-wide admin consent.