For a more detailed look at your desk usage, admins can download a copy of desk reservations in CSV format via Analytics > Exports > Desk 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 6-month date range
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.
As of August 2022, Admins can now export desk data for a specific building or all buildings. Note: this feature already exists for Activity summary.
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.
1. Select the Desks tab.
2. Select the date range, up to 90 days in the future.
3. Select a specific building.
4. Click Email CSV to download a link.
5. You'll receive an email with a link to download the report. Note, that the link expires after 24 hours.
Desk history data breakdown:
|Organization||This is the name of the organization where the desk reservation took place.|
|Building||The name of the location the desk resides in.|
|Floor||The level the desk resides in.|
|Desk Group||The name of the group the desk resides in.|
|Desk ID||The ID number of the desk in the Robin system.|
|Desk Name||The human-readable name of the desk. This is the desk name that appears in search results and other parts of the user interface.|
|Reservation ID||The unique identifier for each reservation, regardless of type. If the reservation is part of a multi-day series, the Series ID appears as a prefix followed by a formatted timestamp that represents the start time of that specific instance in the recurring series.|
|Series ID||For multi-day desk reservations created on the web (and coming soon, mobile), this is the unique identifier for the reservation as a whole. For single-day desk reservations and older, non-recurring reservations (where a multi-day reservation was a single, continuous block of time), this is blank.|
|Type||Hot, Hotel, or Assigned.|
|Start||When the desk reservation started. Reported in UTC time.|
|End||When the desk reservation ended. Reported in UTC time.|
This is the duration of the desk reservation specified in hours down to 2 decimal places. This includes hot, hotel, or shared desks ("reverse hoteled") reservations. This field will be blank for assigned desks.
|Checked In At||The time at which a reservation was manually or automatically checked in.|
The time at which a reservation was canceled by a user.
This indicates how the reservation was canceled. There are 2 types:
|Creator Name||Name of the person who made the reservation.|
|Creator department||All departments that the creator is associated with. If a user is associated with more than one department, the department names will be separated by commas. Note, department information is only reflected for Enterprise customers using OKTA and Azure AD.|
|Creator Group||All groups that the creator is associated with. If a user is associated with more than one group, the group names will be separated by commas.|
|Creator Email||Email of the person who made the reservation.|
|Assignee Name||Name of the person for who the desk reservation was for.|
|Assignee department||All departments that the assignee is associated with. If a user is associated with more than one department, the department names will be separated by commas. Note, department information is only reflected for Enterprise customers using OKTA and Azure AD.|
|Assignee 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.|
|Assignee Email||Email of the person who the desk reservation was for. This includes non- Robin users who are assigned a desk by an email address only.|
The export will look something like this:
Any new or modified reservation made in Robin will not be reflected in an export until the following day. Data is synced overnight between 9pm EST and 9am EST.
It’s Monday morning and a user decides to book a last-minute desk for this afternoon. As an admin, if you downloaded a desk export for today's date, you would not see this reservation in the export until tomorrow morning because the data has not been synced.
Last week, a user booked a desk one month in the future but decided to modify the reservation earlier this morning. If an admin pulled a desk export today, they would not see the modified reservation until the following day because the data has not been synced. The export would reflect the state of the reservation as of yesterday.