Reserve - Reservation Protection

Reservation Protection in Tango Reserve

Reservation protection allows customers to limit which applications can create, modify, and end reservations.  This can be accomplished by selected the allowed applications to an asset.  Reserve can then allow/disallow reservation management based on the application.  If the list is empty (the default) then there are no restrictions as to which application can manage reservations for that asset.

Example Use Case

In your building, there are Huddle Rooms that can only be booked just-in-time by an employee by walking up to Room Kiosk iPad outside of the room. These rooms cannot be booked in advance via the Classic Web, Mobile app or any other Reserve interface except via the tablet. Instead, these are “first come, first-served” rooms that the users can book before walking into the room. In Reserve, the Reserve Administrator with the right to Manage System and Manage Assets right would check the box for iOSRoom Kiosk only. This means that users will only be allowed to book on the iPad but not from the other interfaces like the Web or Mobile app.

Initial Setup

1. The Tango Reserve technical team sets ‘reservation.protection.show’ to true to display the reservation protection option.
2. A user who has MANAGE_ASSETS and MANAGE_SYSYEM rights will have the ability to specify which applications will allow the creating and management of reservations for a given asset.
3. Once enabled, the user will see a new option called ‘Reservation Protection’ within Settings → Assets → Open the Asset record → Reservation Protection.
4. Within the table, select the applications to be used to modify requests and reservations for this asset. Users will not be able to modify requests or reservations for this asset via any application which is not selected. Using the earlier use case, this means that only the iOS Room Kiosk application would be selected.

Applications that Impact Reservations

1. 508 Application (Accessible Interface)
2. Agilquest.com (Reserve Classic Web)
3. Android Mobile
4. Crestron Fusion Connector
5. Crestron Room Kiosk
6. DataManagementAPIService
7. DeskMate Pro for Android (Desktouch)
8. DMU
9.  Exchange Connector
10. Google Connector
11. iOSMobile
12. iOSRoom Kiosk
13. Lobby Kiosk
14. Outlook Plug-in
15. PLAI Listener Service
16. Steelcase RoomWizard Connector
17. WinRoomKiosk

Considerations

• If you have developed an integration with Reserve involving the creation, management or ending a reservation, you may need to select the ‘DataManagementAPI Service’ option. It is recommended that you do an initial test with it unchecked to ensure that you can continue to use your solution and if needed and if needed, select this option.
• If you use First Swipe or Open Presence Listener to automatically check in to reservations, you will need to enable the PLAI Listener Service.
• When Reserve Classic Web is disabled, and the M365 Connector is being used:
  • Don't use Requests with Reservation protection when Classic Web is disabled. This is because when a booking is made in Outlook to sync with Reserve, when the approver declines the request, the room is not removed from Outlook which could make it appear to the user that the room is booked, when it isn't. 
  • When a conflict occurs and the room is not booked and is rejected by Reserve, there booking does not write back to the Outlook calendar. 
  • Links are not added to the invite when booked through Outlook.

Attachments (2)

69a68a11890ac.29481879264787.jpeg
225 KB

69a68a11890af.29481879267475.jpeg
168 KB