Limit the amount of concurrent bookings under one person's name. Only book one (or however many desks) under your own name, all others under other people's only.

Apply the set concurrency limit against the person that has been "booked for" (not the person doing the booking on behalf of another). If the concurrency limit is "1", then any user should not be able to book more than 1 seat, regardless of whether they booked by themselves or if another booked on their behalf.

When I am making a booking on someone elses behalf, I should only be able to book in the desks that that person would normally be able to book in

This should also apply to making bookings via the Kiosk

Working as intended now, but perhaps this behavior should be changed for users booking for themselves AFTER their supervisor (with BOBO) has made an appointment for them.
Supervisors with BOBO should be able to bypass concurrency for other users, but those users should not be able to book for themselves once they have a booking at the same time.

Apparently the Secured Action of "Reservations - Book on behalf of another person" also provides the same permissions as if they are also assigned the Secured Action of "Reservations - Bypass concurrency limit", BUT without actually assigning the second Action.

I would like to need to manually assign the second Secured Action to a Security Role, rather than allow it to happen automatically. I have over 1300 people that have the ability to Book on Behalf of another person, but only a very small subset that I want to be able to bypass the occupancy limit. But I don't have that ability the way the system is currently configured.

Because the second Secured Action is already in the system, I'm not sure why the bypass was put in place, rather than requiring it be assigned to a Security Role, as is the case with the first Secured Action.

It would be great for the email confirmation to be able to be CC'd to the person booking on behalf of someone else so they know the booking is confirmed currently they cant see and have to assume it is ok. Those using this function in our organisation would mainly be EA's to Exec so they really need to know the booking is confirmed and manage the diary of the Exec

Instead of filtering based on all bookings in Engage it would be great to have the ability to filter based on an individual employee you have booked for. Some team members book on behalf of multiple employees and would like to see just one employees bookings instead of all bookings.

When booking a desk on behalf of somebody else both the email they receive and their Manage bookings panel should reflect who made the booking for them. The same should should apply if the booking is cancelled by the delegate. Currently the booking recipient has no idea who made the booking for them

Allow staff that can "book on behalf of", to also "Cancel on behalf of".

Example, an Admin books an office for their VP. but the VP needs to cancel, the admin now cant cancel that booking that he/she made.

Currently users that are opted out cannot be booked on behalf of. The user case is, users want to be hidden from search results but still want a PA to book a desk for them.

Our change champions are making multiple bookings on behalf of their team members, as well as for themselves. They have asked if the 'book on behalf of' entries in the calendar could be a different colour or more distinct?

Our change champions are making multiple bookings on behalf of their team members, as well as for themselves. They have asked if the 'book on behalf of' entries in the calendar could be a different colour or more distinct?