Admin privileges required to enable integration between Google Workspace and Roomzilla

You are here:
< All Topics

What permissions does a user account in your corporate Google Workspace need to integrate with Roomzilla?


We recommend the Google admin account used to authenticate the integration is dedicated solely for integration purposes and is not used as a regular user within the application, e.g. admin@yourdomain.com. This email address isn’t required to be, and shouldn’t be, utilized as a Roomzilla user account.

 

Users without any administrative roles are unable to grant Roomzilla the necessary integration permissions. Ensure that you have a role equipped with the appropriate permissions before moving forward with the integration process.

 

 

There are two ways to accomplish this:

1. Super Admin role – The quickest and easiest option is to integrate using an account with the Super Admin role in Google Workspace.

Note: While integrating, Roomzilla receives a token for a few specific permissions (as shown below) rather than obtaining full super admin access. It’s most convenient to utilize the Super Admin account since it doesn’t require additional steps on Google’s side.

For more information about access consent for Google Workspace, please refer to this link.

 

2. Custom Admin role with access to the resource calendars.

To integrate Roomzilla with Google Calendar in this case, you’ll need a role that grants specific permissions, as outlined below (A), as well as additional permissions for each individual resource calendar (B).

A: [Google Workspace Admin panel > Account > Admin roles > Create new role]: The required privileges are limited to Users (which include groups in both Admin console privileges and Admin API privileges) and read access to Organization Units.

 

B: [Across all integrated resource calendars]: The admin authenticating Roomzilla integration with Google [4] must have permissions [5] to make changes and manage sharing settings of each resource’s calendar – configured separately for each resource: