Integrations - General Specifications

Integrated spaces

Spaces that are integrated, do not exist in Skedway, they are from Google/MS. The account is created in the Google/MS platform and linked to an resource inside the Skedway, so we can apply all the management and the layer of rules. Ex.: sala01_3746167751896541@resource.calendar.google.com. It can be seen that the email is from the domain is from google, the term they use is resource.calendar

Skedway integrates both calendars and users, and only with ONE PLATAFORM ACCOUNT, this means it will connect with a Google Workplace or Microsoft. If you have more than one, you will have to choose one of the accounts to integrate, or use the standalone format (not integrated).

Domains (Domain-Wide Delegation of Authority)

Skedway uses the Wide delegation configuration as it covers all subdomains and thus we guarantee that no user/room is left out of the integration.

Skedway will have access to all users and rooms calendar in the account, and this is the only way we will be able to compare schedules and cross check events with each person.

Skedway does not release permissions at the user level, that is, each user who will authorize Skedway to access their schedules.

Pratical validation

To validate that the integrations are working, it will be necessary to have a user who is registered both on the integrated platform (MS or Google) and on Skedway. This user must view, create and change events within Skedway, and they will be directly reflected on these platforms, and vice versa. Remembering that only appointments made in integrated spaces will be reflected.

Impact

If the ACCESS PERMISSIONS present any failure or error, the user and space calendar that are integrated will no longer be visible and bookable within Skedway. This requires an analysis of each case.
Users and rooms that are not in the Google/MS database will not be able to view, schedule or invite other integrated users and spaces.
The Skedway`s rule will only be applied in the integrated spaces when they are booked by Skedway, if the space is booked by the integrated platform, Google/MS, the scheduling is saved directly on the platform and then synchronized, not passing through Skedway.
When scheduling is done through an integrated space, sending event invitations (.ics) is the responsibility of the integrated platform, that is, Skedway will not send the event invitation precisely so that users do not receive duplicate information. Skedway only sends the inform invitations, updates and reminders.

Error

Here are some error messages that may occur at the time of implementation.

Message: {“error”: “access_denied”,“error”: “access_description”: "Requested cliente not authorized.”,} This means that the account entered in the integration by the client cannot release the necessary scopes and permissions of the users and calendar data information by Skedway. To do so, request a review of that user's access permissions on the integrated platform, as there are no impediments on Skedway's side. This message appears when a manager client enters the integration settings and performs manual verification through the "TEST" option. ADMINISTRATION > INTEGRATION >TEST. The email entered must be the same email registered to release permissions.
Message: “User removed or does not exist in integration with [Google/MS]" This means that Skedway was unable to locate the user's account on the integrated platform, it can have two origins, either the user does not exist on the integrated platform side or he is removed/disabled, preventing Skedway from locating him. This message appears when entering user registration settings, ADMINISTRATION > USERS. PS: This deactivation is not the same as the normal managing a user procedures through the system where he can no longer use the system, it is a technical deactivation of communication between Skedway and the integrated platform and needs to be analyzed in detail.

PreviousUtilities NextGoogle Workplace Integration - Calendar + Directory

Last updated 1 year ago

Domains (Domain-Wide Delegation of Authority)

Skedway uses the Wide delegation configuration as it covers all subdomains and thus we guarantee that no user/room is left out of the integration.

Skedway will have access to all users and rooms calendar in the account, and this is the only way we will be able to compare schedules and cross check events with each person.

Skedway does not release permissions at the user level, that is, each user who will authorize Skedway to access their schedules.

Pratical validation

Impact

If the ACCESS PERMISSIONS present any failure or error, the user and space calendar that are integrated will no longer be visible and bookable within Skedway. This requires an analysis of each case.

Users and rooms that are not in the Google/MS database will not be able to view, schedule or invite other integrated users and spaces.

The Skedway`s rule will only be applied in the integrated spaces when they are booked by Skedway, if the space is booked by the integrated platform, Google/MS, the scheduling is saved directly on the platform and then synchronized, not passing through Skedway.

When scheduling is done through an integrated space, sending event invitations (.ics) is the responsibility of the integrated platform, that is, Skedway will not send the event invitation precisely so that users do not receive duplicate information. Skedway only sends the inform invitations, updates and reminders.

Error

Here are some error messages that may occur at the time of implementation.

Message: {“error”: “access_denied”,“error”: “access_description”: "Requested cliente not authorized.”,} This means that the account entered in the integration by the client cannot release the necessary scopes and permissions of the users and calendar data information by Skedway. To do so, request a review of that user's access permissions on the integrated platform, as there are no impediments on Skedway's side. This message appears when a manager client enters the integration settings and performs manual verification through the "TEST" option. ADMINISTRATION > INTEGRATION >TEST. The email entered must be the same email registered to release permissions.

Message: “User removed or does not exist in integration with [Google/MS]" This means that Skedway was unable to locate the user's account on the integrated platform, it can have two origins, either the user does not exist on the integrated platform side or he is removed/disabled, preventing Skedway from locating him. This message appears when entering user registration settings, ADMINISTRATION > USERS. PS: This deactivation is not the same as the normal managing a user procedures through the system where he can no longer use the system, it is a technical deactivation of communication between Skedway and the integrated platform and needs to be analyzed in detail.