FAQ
Functionality comparison of different integration
A1: Under integration “Application permission” and “Delegated permission”: create booking of Outlook room on ONES
A2: Under integration “Application permission” and “Delegated permission”: create booking of Outlook room on Outlook
B: Under integration “Delegated resource only” and “Application resource only”: create booking of Outlook room on Outlook
O: The feature does functional;
X: The feature does not functional;
*: Not fully functional;
Feature | A1 | A2 | B |
---|---|---|---|
Create booking on ONES which reflects to Outlook | O | X | X |
Outlook booking reflect to ONES | X | O | O |
Resources schedule display booking | O | O | O |
Walk-in on player | O | O | O 1 |
Extend on player | O | O | O |
End the booking on player | O | O | O |
Check-in on player | O | O | O |
Recurrence booking policy | O | O | O |
All day booking policy | O | O | O |
Cross day booking policy | O | O | O |
Out of business hour booking policy | O | O | O |
Multiple resources booking policy | O | O | O |
Limit booking date range policy | O | O | O |
Limit booking time length policy | O | O | O |
Limit edit / delete before booking start policy | O | X | X |
Not allow overlap with other bookings policy | O | O | O |
Not allow overlap with bookings that involve resources using this booking policy | O | O | O |
Require check-in policy | O | O | O |
Attendee can check-in, check out or extend booking policy | O | O | O |
Allow early check-out policy | O | O | O |
Allow user on-site extend the booking policy | O | O | O |
Allow booking manager book for user policy | O | X | X |
Allow booking from User app policy | O | X | X |
T&C policy | O | X | X |
Booking approval | O | * | * |
Booking approval (Hold time slot) | O | O | O |
Extra booking form field | O | X | X |
Booking pin | O | X | X |
Email style | O | X | X |
- Due to the limitation of permission, the "Walk-in on player" feature can only reserve a room without recording who has actually reserved the room.↩