Google Integration

Why does Coworking Access Control Sync require all of these permissions from Google?
- <INSERT screenshot of Google permission screen here>
- 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 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. 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.
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.

System Requirements

Why is a Windows PC required?
- There is nothing inherent to CACS that needs Windows or .NET. We chose .NET and Windows mainly because coworking facilities with Isonas Access Control already have a Windows PC there running the Crystal Matrix software. Rather than add to the list of software platforms someone needs to keep up to date, we went with windows.