Anonymousprnt::Y
Click on images to see them in full screen

Enable access

By now you would have:
  1. Created resources such as rooms and desks. See Database 'Door Tablet HELP', View 'Help Documents', Document 'Create Resources'
  2. Enabled API access to your resources. See Database 'Door Tablet HELP', View 'Help Documents', Document 'Enable API Access'
  3. Prepared your preferred authentication method. For 2-legged see here Database 'Door Tablet HELP', View 'Help Documents', Document '2-legged Authentication' and for 3-legged see here Database 'Door Tablet HELP', View 'Help Documents', Document '3-legged Authentication'

You are now ready for the final step.

Enabling Security between the Calendar API and your Room Resources
Login to the Admin console of Google Apps for Business (https://admin.google.com), then click on Security:


Expand the options and click on Advanced settings



Authorise the Google Calendar API to access your Resource Calendars



You need two data items:
  1. The CLIENT ID from the Service Account
  2. The API scopes listed here:
https://www.googleapis.com/auth/calendar.readonly
https://www.googleapis.com/auth/calendar.events
https://www.googleapis.com/auth/gmail.compose

Copy the above and add a comma to separate them, like so
https://www.googleapis.com/auth/calendar.readonly,https://www.googleapis.com/auth/calendar.events,https://www.googleapis.com/auth/gmail.compose


As you can see, Gmail is also included in the authorisation. This is so since Door Tablet will use your Gmail to send email messages about various events such as check-in reminders.


Create an Account user
This user is required for sharing. Create the user and make a note of the email address, it will be required in:
  1. Door Tablet server system profile
  2. Calendar Sharing in Google Calendar
Steps:
Open the Google Apps for Business dashboard
Click on Users

Click on the plus sign to add a user


Note: we have used the name dt_service but you can have any unique name you like. No need to set password or additional info.
The email address showing here, in this case dt_service@publicclass.co.uk, will be required by Door Tablet, marked a item 3 (at the very end of this document).




Sharing Calendars with an Account User
In the step we will need to create a user in the Google G Suite and allow it to share each of the Calendars. Before we do this we need to include all the Calendars in the administrator My Calendar. Follow these steps:

Open your Calendar (as Administrator)


Prepare to add the Resources Calendars


Look for More Calendars

Click on Resources for your Domain name

You will need to Subscribe to each Resources

Share the Calendars you have Subscribed to
  1. Go back to your Calendar and all the Resources will be shown as Additional Calendars
  2. You will now need to set each to share to the dt_service email address


Sharing the Calendar



After you share, each of your Meeting Room Resources will become visible to Door Tablet.

Conclusion
In this section you have completed preparing G Suite for use by Door Tablet. You are now in possession of the three items:
  1. The Service Account EMAIL ADDRESS
  2. The Google Service Account email address
  3. The P12 file with your private key.
You are now ready to proceed with Door Tablet server configuration

Setting the Door Tablet server to connect Google
  1. Open the system profile and fill the three items as shown
  2. Before you test your connection for the first time, save the profile
  3. Open the system profile again and click on Check Connection to Google
  4. You can now go to one of the space view and hit Synchronise
Pat your self on the back - you are done



When you hit on the Synchronise button Door Tablet will connect to Google and get all your rooms.



Result...


You are now able to open each meeting space, activate and configure as you see fit.

Adding rooms later
You can add meeting space and easily introduce them to Door Tablet. Back in your calendar, set the calendars to be shared with the service account. If you did not pay attention you will not give the service account enough permission to update events:

In such a case, you need to update the entry. If you can edit the entry, remove it and add it again:


And the result...