...
If the reservation as a whole needs to be approved, the task for the reservation coordinator(s) will be generated. If any specific reserved object also requires approval, a separate approval task is generated for each of the applicable reserved objects.
Any tasks to handout/prepare reserved objects are generated and handled
If the reservation is completely approved (or no approval was needed) and the generation of tasks for the handout/preparation of any reserved objects is applicable, these tasks are generated for the relevant users.
The reservation takes place
...
For more information about registering visitors, see Visitor module
Confidential reservations
When creating a new reservation, either via Workplace management, Workplace Experience or if done via Outlook or Google calendar (if an integration with one of those external calendars is set up) it is possible to mark a reservation as confidential / Private.
When a reservation has been marked as confidential, the confidential details* of the reservation are hidden from other users, with the expectation of the following users:
The requestor of the reservation
The creator of the reservation (often also the requestor)
Any participants added to the reservation (via Workplace Experience or an external calendar)
Admonitors
Any users that have been added to a system group that has been marked as the system group that has access to confidential reservations. This could for instance be used to grant reservation coordinators access to confidential reservations, such that they can inform the relevant employees if a reservation has to be changed or canceled.
This group can be specified via the reservation module settings, by default this field is empty:
...
*The following details of a confidential reservation are hidden from other users:
Requestor
Subject
Description
Details
Any participants linked to the reservation
N.B if a recurring reservation is marked as confidential (via the reservation template) the recurring reservation itself is hidden from other users. For each of the occurrences, the same logic applies as for a single reservation (as described above)
2. Automatic emails send in the workflow(s)
...