Skip to main content

Admin and Booker Role limitations for creating bookings for Users

This guide will help you understand the limitations for when an Admin or Booker is creating a booking based off their assigned role

Kelley Pembroke avatar
Written by Kelley Pembroke
Updated this week

Relevant roles

  • Admins - can book on behalf of others and approve all bookings

  • Booker - can book on behalf of others

  • Booking approver - can approve bookings for all Users or by department

On-behalf of when booking Users

  • Primary guest - User the booking will be assigned to.

  • On-behalf Booker - User performing the booking, and assigning the booking to the primary guest. This User will be an Admin or Booker.

We calculate almost all limitations based on the primary guest during an on-behalf booking.

These are the exceptions

  • HQ desk assignment - on-behalf-booker with Admin or Booker role can override.

  • HQ booked another desk / private office - on-behalf-booker with Admin or Booker role can override.

  • Company budget limits - on-behalf-booker with Admin role only can override.

Other than these exceptions, all limitations are calculated by the primary guest role and are NOT overridden by the on-behalf-booker role

Some examples of those:

  • multiple seats in common space (flex)

  • space types

  • company limits (budget) - if on-behalf-booker has Booker role

  • space in a location that is not exposed to company

  • geo-fence

  • space in company's spaces to exclude list

Regarding Admin approval for on-behalf bookings


If according to the primary guest an Admin approval is required, the logic is as follows:

  • If the on-behalf-booker is Admin - we will NOT require admin approval

  • Otherwise, we will require an Admin approval.

For example:


In a test company, if Admin approval is required for bookings above $100. For this test company, we have the following Users roles set up:

  • User A - Regular User

  • User B - Booker

  • User C - Admin

  • User D - Booking approver

If User A books for themself - An Admin approval will be required.
If User B books on behalf of User A - An Admin approval will be required.
If User C books on behalf of User A - An Admin approval will NOT be required.
If User D tries to book on behalf of a User - They are unable, as this role cannot book on behalf of User A because they are not an Booker

Still Have Questions? Please reach out to us at support@gable.to

Did this answer your question?