People export

Supported Plans

  • Starter
  • Teams
  • Enterprise

The People export helps teams like admins and office managers look up when someone was in the office according to their desk reservations/assignments.

Admins can download a copy of a specific user’s desk reservation history in CSV format via Analytics > Exports > People tab. This feature is available for Teams plans & above, with total time range available increasing per plan. The max amount of data that can be requested per export, regardless of your plan, is 6 months. 

  • Teams: 60 days back

  • Enterprise: Any date range of 6- months.

 

Export enhancements

In December 2022, we raised the date range limit for analytics data exports from 45 days to 6 months. Teams accounts can request data up to 60 days back and Enterprise accounts can request data for any 6-month time range. For example, as an Enterprise customer, I want to export a year's worth of historical data; this means I need to generate 2 different reports. 

 

Watch the quick tutorial or follow the guide below

 

 

1. Select the date range up to 90 days in the future.

2. Enter the user's name or email for non-robin users.

3. Select Email CSV.

4. Then you'll receive an email with a link to download the report. Note, that the link expires after 24 hours.

2022-08-23_08-02-19.png

Common Pitfalls

The data is stored in UTC. We recommend adding an additional day on each end of the export date range to ensure all relevant data is included for your timezone.

 

Export breakdown of a single person

Keep in mind, that if a person has two desk reservations they'll be listed twice in the export to provide full visibility into all the places a person was sitting for contact tracing purposes.

  • Day: The date the desk was reserved for.

  • Name: The name of the user searched for. Note, 

  • Email: Email address of the user searched for. This includes non- Robin users who are assigned a desk by an email address only. 

  • Building: The name of the building the person booked a desk in.

  • Floor: The name of the floor the person booked a desk on.

  • Group(s): All groups that the assignee is associated with. If a user is associated with more than one group, the group names will be separated by commas. 

The export will look something like this:

ppl_export_part_I.png 

If you want to know who else booked a desk the same day in the same building and on the same floor as a specific user over the same date range,  select the Include Nearby People check box.

ppl_export_part_II.png

Export breakdown with "Include others nearby"

  • Date: When the desk was reserved for.

  • Name: The name of the user searched for.

  • Nearby People: The names of users who booked a desk in the same building/floor on the same dates as the user.

  • Emails of Nearby people: The email address of the users who booked a desk in the same building/floor on the same dates as the user. 

  • Email: Email address of the user searched for. This includes non- Robin users who are assigned a desk by an email address only. 

  • Building: The name of the building the person booked a desk in.

  • Floor: The name of the floor the person booked a desk on.

  • Group(s): All groups that the assignee is associated with. If a user is associated with more than one group, the group names will be separated by commas. 

  • Desk Type: The type of desk the user occupied; assigned, hotel, or hot. 
Type Reservation Duration Can I reserve in advance? Who can reserve?  
Assigned Permanent Yes  Admin/Roles with delegate access  
Hot 1 day only No  Member, Admin/Roles with delegate access on members behalf  
Hotel 1-5 days or more Yes  Member, Admin/Roles with delegate access on members behalf  

 

Why it’s helpful 

If someone tests positive for Covid-19, you can look up when that user booked a desk in the office over a historical date range. If you want to know who else may have come into contact with that user, you can Include Nearby People.

The People export, including others nearby, will look something like this:

ex_ppl_export_II.png

Did this article help?