INTERLOCK

FOR YOUR ORGANIZATION

IT admin guide.

Keep work calendars aware of each other’s busy time without transferring the original meeting information. Review permissions and sharing boundaries before approving access.

Interlock by Provisio Insights is operated by Provisio Insights, LLC. Public support: hello@interlock.nexus.

Review before connecting

A user signs in with a passkey, connects each authorized account separately, selects calendars and approves individual directions after a preview. A direction from A to B does not approve B to A or onward sharing. Source meetings stay unchanged. Destination appointments omit original meeting details, but their Private flag and source account label remain subject to destination access rules.

As of (America/Chicago), Google Calendar access is approved for the current Interlock setup. This does not cover additional applications, permissions or data uses. Microsoft publisher verification and partner enrollment are incomplete. Your organization can still require its own approval. Stop at an unverified-app warning and seek your organization’s review.

Identify the application

Application identities for administrator review
ItemExpected value
Product and operatorInterlock by Provisio Insights · Provisio Insights, LLC
Start addressinterlock.nexus
Microsoft application ID9b37abe9-1b4c-4cb2-892b-7c42ce0d5a8c
Microsoft publisher domainprovisioinsights.com; publisher currently unverified
Microsoft account audienceWork or school accounts in organizational directories (AzureADMultipleOrgs). Personal Outlook accounts are not currently offered.
Microsoft callbackhttps://interlock.nexus/api/microsoft/callback
Google production OAuth client ID38152245841-6gmtm7o3dcl867bhmtet26m673lv1ec1.apps.googleusercontent.com
Google callbackhttps://interlock.nexus/api/google/callback

Match the application ID or OAuth client ID, complete permission request and callback. A matching display name or logo is insufficient. Provider permissions can authorize more event content and actions than Interlock’s intended scheduling-field requests and owned-block controls.

Microsoft 365 permissions

The default synchronization request is openid, profile, offline_access, https://graph.microsoft.com/User.Read and https://graph.microsoft.com/Calendars.ReadWrite. These are delegated permissions acting for the connected user. Offline access supports refresh while the browser is closed; organization policies can require another sign-in.

Microsoft Graph permissions by feature
PermissionWhen requestedProvider capability
User.ReadDefaultRead the signed-in user’s profile.
Calendars.ReadWriteDefaultRead, create, change and delete events in the user’s calendars.
Calendars.Read.SharedOptional shared readingRead accessible shared and delegated calendars.
Calendars.ReadWrite.SharedOptional shared writingRead and change accessible shared and delegated calendars.
MailboxSettings.ReadWriteOptional Outlook colorsRead and change mailbox settings; broader than a color-only permission.

Each optional scope uses the https://graph.microsoft.com/ prefix and is added to the default request for that feature. Leave optional features off unless approved. Calendars.ReadBasic belongs to a separate availability-only mode; it is not the default synchronization request and cannot supply writes. Configured registration permissions do not establish which permissions have been granted. See Microsoft’s permission reference.

Google Calendar permissions

Every request includes openid and email. Google can return the equivalent https://www.googleapis.com/auth/userinfo.email spelling. Background access uses access_type=offline, not an offline_access scope. Calendar scope names below use the prefix https://www.googleapis.com/auth/.

Exact Google calendar scopes by access choice
Access choiceCalendar scopesProvider capability
Default owned calendarscalendar.calendarlist.readonly
calendar.events.owned
List subscribed calendars; read and change events on owned calendars.
Optional shared readingcalendar.calendarlist.readonly
calendar.events.owned
calendar.events.readonly
Add reading across accessible calendars; owned-calendar writes remain available.
Optional shared writingcalendar.calendarlist.readonly
calendar.events
Read and change events across accessible calendars, subject to the user’s rights.

Shared writing requests calendar.events in place of calendar.events.owned and calendar.events.readonly. Listing a shared calendar does not grant write access. The table describes Interlock’s permission choices; availability is shown in the app. Approval of the current setup does not grant additional access or override your organization’s policy. See Google’s scope meanings.

Organization approval

Record approved users, calendar roles, directions, optional scopes, data restrictions and an offboarding owner in your normal change process. Availability and the source account label can disclose information across organizations. Each organization must authorize the proposed use. Shared access must already exist with the provider.

For Microsoft, review the exact enterprise application and its Permissions in the correct Entra organization. Use your existing admin-consent workflow if required. Tenant-wide consent is not a pilot-user restriction by itself; apply approved assignment controls where appropriate. Keep MFA, device requirements and Conditional Access in force. See enterprise application permission review.

For Google Workspace, use Security → Access and data control → API controls → Manage App Access. Locate the exact OAuth client ID, inspect the scopes and review the intended organizational units. Where your policy permits, use Specific Google data for the chosen access profile. Keep Context-Aware Access and other restrictions in force. See Google Workspace app controls.

Interlock does not require Microsoft application permissions, Exchange organization relationships, a broker mailbox or Google domain-wide delegation. Do not broaden organization-wide access or weaken restrictions to resolve a blocked connection.

Onboarding after approval

  1. Complete the available Interlock invitation or account-creation flow and protect the passkey and signed-in device.
  2. Connect one authorized account at a time. Stop if the identity, app ID, permission request or warning differs from the approved request.
  3. Select only approved calendars. For shared calendars, accept the provider’s sharing invitation first, then use Refresh calendars. Request optional access only when approved.
  4. Choose each direction and inspect Preview busy time. For Microsoft scheduling availability, use the user’s primary calendar as the destination. A secondary-calendar overlay does not prove that the primary calendar appears busy.
  5. Enable only the approved directions. Use synthetic events in a pilot approved by your organization to confirm destination blocks and scheduling availability before wider use. Keep existing connections and permissions within the approved scope.
  6. Check sharing state and last successful activity. Successful sign-in alone does not prove synchronization; unavailable or incomplete data remains unknown.

Pause, disconnect and close

Separate actions during offboarding
ActionEffect and limit
PauseStops future updates; existing blocks can remain. A provider request already accepted may finish.
ReconnectRestores permitted access for the same identity; it does not revoke a grant or complete cleanup.
DisconnectChoose cleanup or leave blocks. Saved active credentials are cleared after the recorded disposition; verify cleanup completion.
Revoke provider accessA separate provider-side action. It can prevent cleanup, affect other connections using the grant and leave existing appointments in place.
Close accountPauses sharing, resolves cleanup or leave-blocks and billing obligations, then requires final passkey confirmation. Necessary records remain.

Disconnect does not perform remote Microsoft or Google grant revocation. Complete and verify cleanup before revoking access when blocks should be removed, unless an incident requires immediate containment. Lost access or uncertain ownership can leave cleanup unresolved. Use Microsoft permission review or Google Account connections for provider-side access review.

Hosted data, retention and support

Cloudflare hosts processing, encrypted credentials and synchronization state. The service can decrypt credentials and process availability while the browser is closed. Provider grants are broader than Interlock’s product controls. A compromised service or authorized token can exercise the granted permissions.

Retention has category-specific periods, approved targets and exceptions for unresolved operations, safety records and preservation obligations. Recovery copies and external support copies require separate handling; closure does not promise complete erasure. Read the current privacy and retention policy.

Send the provider name, approximate time and timezone, fixed error code and diagnostic reference to hello@interlock.nexus. Keep credentials, full authorization URLs, codes, calendar screenshots, event details and raw provider responses out of requests. This beta offers no uptime guarantee or security certification and is not approved for protected health information. Do not use PHI.