Understanding permissions to book for others in IBSS

Written By Natalia Povrozniak (Administrator)

Updated at February 25th, 2026

On top of the standard permissions to book for self, users can get extra permissions to be able to book for other people within their organisation. There are the following layers to it:

  • App permission: API.Bookings.BookOnBehalfOf
  • Delegate permission
  • DATAMODEL.Spaces 4 levels of permissions
  • Space ownership per person or role

There are also standard principles that define user options in IBSS:

  • Users can book only where they have access to. This involves space ownership and their level of Spaces.Read rights.
  • Users don't inherit DATAMODEL permissions.
  • If the user has the Booking for someone else permission, they can book for anyone in the organisation.
  • If the user is appointed as a Delegate for a defined Primary User, they can book for self and the primary user only.

Depending on the requirements to what the user or a role should be able to accomplish, do the following:

  1. Define what access to spaces should be for this user or role.
  2. If the user or role should be able to book for other people:
    • Grant them higher DATAMODEL.Space rights.
    • Or provide access to additional spaces.
  3. If the user or role should have more flexibility to book for anyone, they will require the API.Bookings.BookOnBehalfOf permission.
  4. If the user should be able to book for one or a few specific users, appoint the user as a delegate for those specific other users.