Google Workspace: Setup for Biamp Workplace Integration
This guide covers integrating Google Calendar with a Biamp Workplace organization and provides walk-through of the required steps. This is a long procedure broken into four phases.
- Create a Google Cloud Platform project
- Grant service account API access permissions
- Enable ADMIN SKI API
- Upload the JSON files to Biamp Workplace
Phase 1: Create a Google Cloud Platform Project
These steps set up a Project for your Biamp Workplace organization in Google Workspace.
1. Navigate to the Google Cloud Platform and log in using your Google Domain Admin Account.
2. Locate the Create Project button.

3. Enter a name for your Project and press Create.

4. A notification should appear near the top of the screen once the project has been created. Click on the notification to reach the API manager.

5. In the column on the left navigate to Menu Icon -> API & Services -> Enabled API's and Services.

6. Click on + Enable APIS and Services

7. The API Library will appear, search for "Google Calendar API," Select Google Calendar API

8. Select Enable

9. You will need to now to create a service account. Click on the Menu Icon, select IAM & Admin, then select Service Accounts

10. Click Create Service Account. Fill in the Name, ID, and the Description and click Create and Continue

11. Provide a name for the Service Account and press Create and Continue.

12. Give the service account the "Editor" role, and press Continue.

13. Press Done.

14. Make note of the oAuth 2 Client ID it will be used in the following steps. Also make a note of the email as this will be used for the Service Account email.

15. Navigate to Actions -> Manage Details

16. Navigate to Keys -> ADD KEY -> Create New Key

17. Select the Key Type as JSON and Create

18. Save the JSON file locally to your desktop.
- You will need this file when connecting Biamp Workplace to Google Workspace.
Phase 2: Grant service account API access permissions
1. Navigate to https://admin.google.com and click on Security, then select Access and Data Control, and then select API Controls.

2. Select Manage Domain Wide Delegation

Adding API Controls
During the next steps, we will add three API Controls to the oAuth ID of our Service Account from the previous step. The three scopes are:
- https://www.googleapis.com/auth/calendar
- https://www.googleapis.com/auth/admin.directory.user.readonly
- https://www.googleapis.com/auth/admin.directory.resource.calendar
3. Press the Add new button.

4. Add the Client ID (oAuth ID) of your service account when prompted.

5. After adding the Client ID is added, copy each API scope individually into the fields below the ID.

6. Press Authorize
- You will now see the Service Account listed with the 3 Scopes Applied.

Phase 3: Enable ADMIN SDK API
1. Navigate to the Google Cloud Platform and log in using your Google Domain Admin Account.
2. Navigate back to APIs & Services -> Enabled APIs & Services.

3. Select + Enable APIS and Services

4. Search for and Enable the ADMIN SDK API.

Phase 4: Upload the JSON files to Biamp Workplace
This phase sets up the calendar integration in the Biamp Workplace organization and uploads the JSON files saved to your computer after setting up the Google Cloud Platform project.
1. Go to the Biamp Workplace Web Portal and select the organization you are integrating with Google Calendar and the Workspace project you just set up.
2. In your Workplace organization's console, select the Admin tab, then the Organization Settings, then scroll down to Calendar settings.
3. Select the Add integration button.
4. Select the Google option.
5. Enter the resource admin email—this should be an account with Super Admin privileges in Google Workspace (formerly G Suite). It is recommended to create and use a dedicated account exclusively for Biamp Workplace integration.
6. Select the Upload button and select the JSON saved to your computer after setting up the Google Cloud Platform project.
7. Select Save.
8. Once the integration is connected, it may take up to 24 hours for all room resources to populate from the Google Workspace backend. This delay indicates that the integration has been successfully established and synchronization is in progress.
