Robin customers are now able to manually upload access control data to increase the accuracy of historical check-in and office attendance data. Here is everything you’ll need to get started: 

• Access to your badge swipe data. In order to manually upload the data, you’ll need to export a CSV file of the data that includes the following information: 

  • Timestamp 

  • Email address

• Admin permissions with ability to manage integrations

Once you have a correctly formatted CSV file ready to upload, follow these steps to get the data into Robin. 

1. Navigate to Manage → Integrations

2. On the Integrations page, scroll down to the Badge Integrations section and select Manage for Badge Data CSV Import. 

3. Select Upload CSV.

   

4. Select a Location and Door Access Vendor.

5. Choose a .csv file or drag the file into the upload section.

6. Review the file for any errors.

7. Select Import.

Your file will appear in the file list with the file name, building, and file status. For files that encountered an error, you’ll have the ability to review the errors and optionally force a retry. Please note that forcing a retry cannot be undone, and the file will be processed with errors that will either be omitted or can negatively affect your data. In order to force retry, you’ll need to type in an acknowledgment before proceeding.

 

FAQ

Why should I upload historical badge swipe data? 

• Importing badge data from your access control vendor can increase the accuracy of check-in and attendance data. This is particularly helpful for organizations that use permanently reserved desks, have low check-in rates, or have users who come to the office without a desk reservation. 

What type of errors should I be on the lookout for? 

• Using the correct file format is integral in ensuring that high-quality data is uploaded into Robin. Be sure to use the correct column headers and timestamp format and that emails are valid.
• Additionally, you’ll want to be sure that the user emails are valid Robin users and that their default building/location matches the location you’re uploading the file to.

What type of timestamps are supported?

• The upload tool supports both the ISO format as well as Epoch/UNIX timestamp formats.

Why do I need to select a location? 

• You need to select a location because the data is specific to a building. 

• Uploading data with too many alternative locations in the file is a common error.

How long does it take to process the file?

• Depending on the file size, it can be nearly instantaneous to an hour. The file's status will show as pending until it has been processed, at which point it will show as Completed or having an Error status. If a file has been shown to be pending for more than 24 hours, please reach out to support@robinpowered.com.

Can I upload multiple files? 

• Yes! You can upload multiple files for multiple locations. The badge imports page will show previous file names, the building they were uploaded to, and the status of the file. 

How do I know when a file was last uploaded? 

• The Badge Imports page includes columns for time and the uploader.

How is the data used once it is uploaded to Robin?

• The data is used to create check-ins for the users who swiped their badge over the date range provided by the timestamps. If a user had a reservation but did not check in to a desk for the date of the reservation the desk data will retroactively be shown as checked in. If a user did not have a reservation and did not check in to a desk, a visit will be created and checked in and reflect them as having been in the office for that date. This information is then available to be viewed in both analytics and advanced analytics so workplace managers can evaluate their office occupancy with a higher level of confidence. 

If you need further assistance or want to report an issue not covered in this document, please email our support team at support@robinpowered.com.