For IT admins
One of your colleagues uses to keep their availability accurate across the companies they work with.
What it does
It keeps one person's calendars in step.
When your colleague is busy elsewhere, it adds a private block titled Busy to their calendar here, so coworkers don't book over it.
When they have a meeting here, it copies that meeting to their own calendar, so they see their whole day in one place.
Data and control
Copies to their own calendar
Your colleague can turn off copies for your organization, so none of its meetings reach their own calendar. They can also keep any single meeting here by adding #nosync to its title or description.
Where data is stored
Google Cloud, in the United States.
When access ends
When your colleague removes your organization or deletes their account, we delete every copy and Busy block we made, and the saved sign-in for your organization.
Security questions
What it can access
| Google scope | https://www.googleapis.com/auth/calendar.events |
|---|---|
| Microsoft permission | Calendars.ReadWrite, plus sign-in permissions (listed below) |
| Which calendar | The user's primary calendar only |
| Not touched | Mail, contacts and files |
What it writes to your calendars
- Private Busy blocks only, with no titles, attendees or details from other organizations.
- It never sends invites.
- If your organization blocks third-party sign-in, the user can add a busy-only subscription link to their own calendar instead. It holds Busy blocks only, and nothing is written to your calendars.
Busy
Tuesday, November 3, 2–3 PM
- Visibility
- Private
- Shows as
- Busy
- Guests
- None
- Location and notes
- None
- Organizer
- Your colleague
How it protects access
- Refresh tokens are encrypted at rest with AES-256-GCM.
Approve it in Google Workspace
- Open the Google Admin console.
- Go to Security, then Access and data control, then API controls.
- Select Manage third-party app access, then Configure new app.
- Search for the OAuth client ID below.
- Choose who it applies to: everyone, or an organizational unit.
- Set access to Trusted.
Changes can take up to 24 hours to apply.
Approve it in Microsoft 365
- Open the Microsoft Entra admin center, then Enterprise applications.
- Open the admin consent link below and approve for your organization.
- Or, if the admin consent workflow is on, approve your colleague's request there.
| Delegated permission | Why |
|---|---|
| Calendars.ReadWrite | Read the user's calendar and add Busy blocks |
| User.Read | Identify the signed-in user |
| offline_access | Keep the connection without repeated sign-ins |
| openid, email, profile | Sign-in |
Revoking access
Admins and users can revoke access at any time. When a user removes your organization inside , it deletes every copy and Busy block it made there.