Page Comparison

...

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.
   • Examples:
   • 1: User's reservation is from 7am to 7:30am on Tuesday. This will be cleaned up at 8AM on Wednesday.
   • 2: User's reservation is from 4PM to 5pm on Wednesday.  This will be cleaned up at 8AM on Friday.

3. How does CACS setup a reservation start/end time in Isonas?

   • CACS creates a special group Isonas specifically for that user
   • CACS then creates a special shift and permission solely for that group that matches the reservation time

4. What are the LSG and LS groups and shifts in my Isonas system?

   • Please see #3 above.  Please do not manually edit/delete these groups or shifts.

5. How long does the user's ID File, badge, and group remain in Isonas after their reservation?

   • 30 days after their last reservation, the user, their badge, and all of their group memberships will be removed unless they have been added to an ignored group (see #4 below).
   • As long as the user books a reservation once every 30 days, their badge code will be the same (but it will only allow them in the facility during their reservations).

6. What if a permanent member of my facility that already has a badge books a reservation in Liquidspace?

   • The configuration utility allows you to configure an Isonas group of people to ignore.  Every time a reservation is observed from a user in that group, CACS will ignore it completely.  For this to work, ensure the email addresses on your ID Files match those of your Liquidspace users.

7. How does CACS associate email addresses with Isonas ID Files?

   • CACS uses the 'user defined fields' section of the ID File.  It currently will occupy uses up to 3 fields (based on the length of the email address), starting at 'Security Clearance'.

8. What if an ID File already exists with an email address that matches the Liquidspace reservation?

   • If the user is not the ignored group, then the ID file will be used for the user's reservation and then managed according to the schedule noted in question 5 above.

...

1. What does CACS store on my machine and what should I backup?

   • CACS stores all of its data under the AppData\Roaming directory of the user you choose during the installation process.  For most installations, this will be C:\Users\bswcoworksync\AppData\Roaming\BSW Technology Consulting\Coworking Access Control Sync.  You should backup the entire directory.
   • venueinfo.db - This is a SQLite database that contains venue/room calendar settings, Isonas group settings, email templates, and keeps track of both current reservations and inactive reservations from the past 30 days.  Backup this file!
   • isonas.config - This file contains your Isonas hostname, port, username, password (encrypted), and encryption key (encrypted).  If you ever need to reinstall CACS on a new machine, you will still need to run the configuration tool again to reset your password and encryption key.
   • google.api.config - This file contains the access token and client ID that ties your Google account to BSW Technology Consulting's Google account.  If you ever need to reinstall CACS on a new machine, you will still need to run the configuration tool again and re-authorize access to your Google account.
   • logs - Directory that contains information on what the sync tool does as reservations are processed.