Setup, Security & Rollout

This page is for IT, facilities, and Google Workspace admins. For sync timing, the booking lifecycle, and guardrails, see How It Works: Technical Details.

What We Need From You

• Share the calendar

  Share your reservations calendar with our team account and our integration account at "See all event details" (read-only). We'll send you both addresses.

• Allow outside sharing

  If your Google Workspace admin settings block sharing outside your domain, allow it for this one calendar.

• Mark the space

  A consistent way to show which space a booking is for, such as the Location field or a title prefix. We'll agree on this together.

• A contact

  Someone we can reach with questions about the calendar or a booking.

What Gets Installed

• One small program. Installed on your building automation supervisor. It adds, updates, and removes our one-time events on approved schedules.
• A dedicated service account. Used only by our connection, so its activity is separate from your staff accounts.
• A private, encrypted network path. Between our cloud and your supervisor.
• Nothing else changes. Your controllers and weekly schedules are not changed.

What Access We Get (and Don't)

Security & Data Handling

• All connections are encrypted.
• Our integration credentials are kept in a managed secrets vault, never in code.
• Calendar access is read-only and limited to the one calendar you share.
• Our building connection only accepts your supervisor's known certificate.
• We store only what we need to keep bookings in sync: the event ID, title, space, and time.

For our broader security practices, see the Cybersecurity & Resilience Program.

Rollout Plan: What Happens After Approval

Once you approve the design, we work through these phases together. Each one has a clear finish line.

1. 1
   Design approval YouSCADA Connect

   You review these pages and the design with us. We agree on scope: which spaces.

   Done when: Written approval to proceed

2. 2
   Calendar access You (Workspace admin)

   We provide two read-only addresses: our team account and our integration account. Your Google Workspace admin shares the reservations calendar with both at "See all event details" and confirms outside sharing is allowed for that calendar.

   Done when: We can see booking details, not just busy blocks

3. 3
   Discovery YouSCADA Connect

   We review real bookings with you and agree how staff mark which space a booking is for (for example the Location field or a title prefix). We also settle the decisions listed below.

   Done when: Space-naming convention agreed and documented

4. 4
   Map spaces to schedules SCADA ConnectYour building automation team

   With your building automation team, we match each approved space (for example Gym, Cafeteria) to its schedule in your building automation system.

   Done when: Every approved space has a confirmed target schedule

5. 5
   Build and test SCADA Connect

   We install one small program on your building automation supervisor and set up a dedicated service account for our connection. Then we test end to end on a dedicated test schedule only. No live spaces are touched.

   Done when: Test bookings create, update, and cancel correctly on the test schedule

6. 6
   Pilot YouSCADA Connect

   We turn on one space (for example the gym) for a trial period. Staff book as usual, and we check each booking against the building schedule.

   Done when: Pilot bookings scheduled correctly for the trial period, with no missed events

7. 7
   Go live SCADA Connect

   We turn on the remaining approved spaces and confirm alert contacts.

   Done when: All approved spaces live and alert contacts confirmed

8. 8
   Ongoing SCADA ConnectYou can pause anytime

   We monitor every booking, alert on failures, and review with you periodically. You can pause the integration at any time by un-sharing the calendar.

   Done when: Ongoing

Decisions to Agree in Discovery

A few booking types depend on how your spaces are used. We agree on these with you before go-live.

• All-day bookings. Whether an all-day booking should condition the space, and for which hours.
• Bookings past midnight. How to handle a booking that starts on one day and ends on the next.
• Tentative bookings. Whether bookings marked tentative should be scheduled.

Next: How It Works in Detail

• How It Works: Technical Details Sync timing, what happens when a booking is created, changed, or cancelled, event naming, and the guardrails that protect your schedules. Read the technical details →
• Calendar-Driven HVAC Scheduling The overview: what it does, how it works in three steps, and common questions. Back to the overview →