We'll see how easy it is to deploy Comeen in your company through the Google Workspace Marketplace.

Google Workspace Marketplace is great to deploy easily an application that extends Google Workspace easily and quickly.

Our integration with Google Workspace is made of:

  • a Google Calendar add-on,

  • a Google Chat bot,

  • a service account,

  • an AppScript application.

Before deploying our application, you'll probably have some questions about the data we collect and how we use it in our product.

Keep in mind that you can access our EULA and Privacy Policy.

To be deployed in your company, your Google administrator needs to accept the following scopes from Google:

  • Google Calendar: See, edit, share, and permanently delete all the calendars you can access using Google Calendar

Why do we need this scope?

Our product needs to create a Calendar called Comeen for each user. This calendar is used for storing next presence at the office (when you use Comeen Today) and desk details (when you use Comeen Desks). We do not create events in the personal calendar of the logged in user to avoid overloading it.

Google doesn't provide a more specific scope such as "See, edit, share, and permanently delete a specific calendar you can access using Google Calendar".

  • Google Calendar: Run as a Calendar add-on

Why do we need this scope?

Our product's main interface is based on a Google Calendar add-on.

  • Google Calendar: View and edit events on all your calendars

Why do we need this scope?

We need this scope to create events in the Comeen calendar of the logged in user (for Comeen Today and Comeen Desks).

We also need this scope for Comeen Visitors: we edit an existing event from the connected user's personal calendar to store a private metadata that lets us know the event has registered external visitors.

Google doesn't provide a more specific scope such as "View and edit events on a specific calendar".

  • Google Admin: View group subscriptions on your domain

Why do we need this scope?

We need this scope to see if a user is subscribed to a Google Group synced with Comeen.

  • Google Admin: View groups on your domain

Why do we need this scope?

In Comeen spaces, an administrator can define end-user right by adding them to a user or a group of users. We need this scope to let admin users of your Comeen space synchronise some Google Groups as Comeen user groups to be able to easily define user rights. When a Google Group is synchronised, all the user in the group become Comeen users.

  • Google Admin: View calendar resources on your domain

Why do we need this scope?

We need this scope to let an administrator of a Comeen space synchronise meeting rooms and linked calendars.

Comeen Rooms lets an end-user book a meeting room with specific criteria (such as: capacity, building, floor, equipment) from our Google Calendar add-on. Comeen Rooms offers a wide range of smart features around room booking: Google Chat notification before meeting, check in, autorelease.

  • Google Admin: See info about users on your domain

Why do we need this scope?

When an administrator of a Comeen space synchronises Google Groups as Comeen user group, for each member of the group, we create a Comeen user. We synchronise: first name, last name, email, phone number, building.

  • AppScript: Connect to an external service

Why do we need this scope?

We need this scope to let our AppScript application communicate with Comeen API.

  • AppScript: View your country, language, and timezone

Why do we need this scope?

We need this scope to use the right language and timezone in our Google Calendar add-on and Google Chat bot.

  • Connected user: See your primary Google Account email address

Why do we need this scope?

We need this scope to synchronise end-user email address.

  • Connected user: See your personal info, including any personal info you've made publicly available

Why do we need this scope?

We need this scope to synchronise end-user details.

Did this answer your question?