By integrating Google Calendar with VergeSense, you gain insight into the effectiveness of your space booking policies by comparing scheduled bookings with real occupancy data. You can further eliminate unused workspaces by configuring business rules that automatically release scheduled resources based on person count, active occupancy, and passive occupancy.

To activate and configure the VergeSense + Google Calendar integration, follow these steps:

Step 1: Authentication

1. Navigate to VergeSense > Settings > Integrations.
2. Click Connect for Google Calendar.
3. Choose the connection mode that fits your use case and click its Start button. You can change your selection later without disconnecting.

Connection Modes

During authentication you choose between two modes, each requesting a different set of OAuth scopes:

Analytics Access (Read-Only)

Enables Utilization Dashboards. Requests:

• https://www.googleapis.com/auth/calendar.events.readonly 
  Read-Only access to calendar events on mapped room resource calendars.
   
• https://www.googleapis.com/auth/admin.directory.resource.calendar.readonly
  Read-Only access to discover and list room resources during space mapping.

Analytics & Actions (Read & Write)

Enables Utilization Dashboards, No-Show Cancellation, and Early Release. VergeSense requests the following scopes:

• https://www.googleapis.com/auth/calendar.events
  Write access to cancel or release events on mapped room resource calendars (replaces the read-only calendar scope above).
   
• https://www.googleapis.com/auth/admin.directory.resource.calendar.readonly 
  Read-Only access to discover and list calendar room resources during space mapping.

Step 2: Map Spaces

When you connect, VergeSense imports your Google Calendar room resources so you can map them to your VergeSense spaces. On request, VergeSense can also run a one-time automatic match that links rooms to spaces by name (matching on any portion of the name, case- and punctuation-insensitive) - contact your VergeSense representative if you'd like this run for your account. You can review or change any mapping at any time.

To map spaces:

1. Go to VergeSense > Settings > Integrations and click Settings for Google Calendar.
2. On the Space Mapping tab, click Map Spaces for a floor.
3. Review the space names and types (pulled from Building Settings). You can filter by status (Connected / Not Connected) or by space name/type.
4. Map each space by picking the matching Google Calendar resource from the dropdown.

Step 3: Configure Reservation Actions

Mapped spaces automatically receive your company default reservation actions. Use the Automations tab to set those defaults and to override individual spaces.

1. Open the Automations tab (section heading "Booking Automation").
2. Set your Global Space Type Defaults - edit the "All types (default)" row (or a specific space type) to configure the no-show grace period, early-end grace period, minimum/maximum reservation length, and whether passive usage counts as active, then click Save Changes. Google Calendar supports No Show Cancellation and Early Release.
3. Enable or disable the actions per space using the No-Show Release / Early-End Release toggles in a floor's space table (these save as you toggle them).

Step 4: Analyze

Review booking data against real occupancy in two places:

- Reports > Space Booking > Booking Summary - an aggregate dashboard comparing scheduled bookings with real occupancy across your portfolio.
- The Bookings tab in Dashboard, available at each level of the analytics hierarchy (building, floor, space type, space group, and so on). It shows a Booking Data table with Scheduled, Attended, No Show Cancellation, and Early Release bookings per space.

Data Collected and Stored

VergeSense refreshes recent events from mapped room resource calendars about every 15 minutes, plus a nightly backfill of the past 7 days. The following event fields are stored:

Privacy note: VergeSense does not store meeting titles or attendee names/email addresses - only the per-attendee response/optional/organizer flags above. All stored data is AES-256 encrypted at rest and used solely to power space utilization metrics, no-show detection, and automated room release.

Updated June 26, 2026 11:45