What should I do if my customer wants to reconnect to Free/Busy Calendar Access mode
We do not advise that your users switch from Read/Write access mode to Free/Busy access mode. If they have already gone through the compliance journey to connect, they will be enjoying the most seamless experience.
However, this may matter enough to some customers that they would rather downgrade their experience to have less detailed connection with Cronofy.
In the scenario where a user or domain administrator wishes to change their Cronofy connection from Read/Write to Free/Busy access you will need to follow these steps below depending on if the user is connected via Individual Connect or Enterprise Connect.
Individual Connect #
For Individual Connect, you will need to first revoke the current access between your application to either the user’s account. This can be done via the Revoke authorization endpoint.
Once the authorization has been revoked to the user’s account, the user will need to re-authorise their connection via the Free/Busy calendar access mode option. To note, your application will need to request the free_busy_write scope at this point.
After your application has succesfully Requested Authorization and Requested an Access Token for the users calendar via Free/Busy access mode, Cronofy will only be able to read Free/Busy information from within their calendar.
You can identify the access mode that a user has selected within the response of the Request an Access Token itself by checking the parameter named linking_profile with the newly linked profile information which inlcudes the following:
linking_profile.provider_namelinking_profile.provider_service
Both of these will return ms_graph_free_busy or google_free_busy if the user has selected Free/Busy Access mode.
Enterprise Connect #
For Enterprise Connect, you will need to first revoke the current access between your application to the Cronofy service account for the users domain. This can be done via the Revoke authorization endpoint to revoke the service account’s access and all the users connected through it as well.
Once the authorization has been revoked to the service account, the domain’s administrator will need to re-authorise their connection via the Free/Busy calendar access mode option. To note, your application will need to request the free_busy_write delegated scope at this point.
After your application has succesfully Requested a Service Account Authorization and Requested a Service Account Access Token, a new Cronofy Service account will be created for the domain which will be returned within the response of the Request a Service Account Access Token.
Also within the succesful response when Requesting a Service Account Access Token, you can identify that Free/Busy was selected during the authorization by checking value provider_name within the userinfo object which will return either of these two values depending on the calendar provider:
ms_graph_free_busygoogle_free_busy
Now that the authorization has been granted at the domain level, your application will need Request User Access for all the users that were previously connected through the Read-Write service account.
Once this has been succesfully completed the users from that domain’s calendars will now be connected via Free/Busy access to Cronofy.