...

• CACS - Coworking Access Control Sync - The core BSW product
• ID File - Isonas's term for a person/user

Google Integration

1. What permissions does Coworking Access Control Sync require from Google?
   

2. Why does Coworking Access Control Sync require all of these permissions from Google?

   • 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.

3. 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.

Reservation Process

1. When do Liquidspace users receive their badge code?
   • 48 hours before their reservations begin, the user receives an automated email (format is customized by you for your facility)
2. How long does the shift and permission remain in Isonas after their reservation?
   • The first 8am time slot that comes around once 24 hours has passed since the end of their reservation.  For example, 
3. How long does the user's ID File / person record remain in Isonas after their reservation?
   • TBD
4. What if a permanent member of my facility that already has a badge books a reservation in Liquidspace?
   • TBD
5. How does CACS associate email addresses with Isonas ID Files?
   • TBD
6. What if an ID File already exists with an email address that matches the Liquidspace reservation?
   • TBD

System Requirements

1. 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.

...