...
What permissions does Coworking Access Control Sync require from Google?
Why does Coworking Access Control Sync require all of these permissions from Google?
- Calendar - CACS does not talk directly to Liquidspace. Instead, it watches a Google Calendar (that you have LiquidSpace sync to) for booked reservations.
- Manage my email - In order to sidestep spam problems, when View and manage my email
When CACS emails the person that booked reservation with their badge info, it is desirable to use your facility's email address as the 'from address.' This increases the likelihood that the user will recognize the email and reduces the chance of spam filters catching it. In order to do that, CACS must authenticate to Google's SMTP servers. Google provides a way for CACS to send email on your behalf without giving CACS your Google password. The problem is, Google does not currently differentiate between giving CACS access to send email on your behalf and the permission to read your email. See this link @ Google for more information. Unfortunately, what this means is that for the moment, you just have to trust that we're not reading your email. That is far from ideal and you shouldn't have to do that. As soon as Google splits IMAP and SMTP OAuth scopes, we can change this. In the meantime, we decided the tradeoff is worthwhile. - Know who you are on Google
Required to obtain your username in order to send email using the approach noted above (SMTP/XOAUTH) - View your email address
We use this to obtain your username from Google to populate the 'from address' on the emails mentioned above - View your calendars
CACS does not talk directly to Liquidspace. Instead, it watches a Google Calendar (that you have LiquidSpace sync to) for booked reservations.
How do I view what emails have been sent by CACS?
- Emails sent to users will be visible in the 'sent mail' of the Google account you configure in the tool, just like ordinary emails.
...