--- title: "Additional Resource Configuration" canonical: "https://docs.cuesystem.com/space/TAM/2756378635/Additional%20Resource%20Configuration" format: markdown --- Resources imported from CUE Calendar or an external calendar server can be supplemented with additional configuration in CUE Admin. This chapter describes the options available on the *Settings* tab that are not synchronized with the calendar server. > ℹ️ These settings are optional, but they enable additional functionality and help ensure that the resource and its reservation workflow behave as expected. Editable fields are displayed with a white background. Fields shown with a gray background are read-only because their values are synchronized from CUE Calendar or an external calendar server and cannot be modified here. ## Reservations ![image-20260803-113654.png](media://000a5cb8-db77-480f-a1e4-dd6b093eedf9) ### Fill available When selected, CUE Assist automatically fills the reservation with the entire available time slot, starting from the earliest possible start time and ending at the latest available end time. These values can be modified before the reservation is saved. ### Default When Fill available is not selected, the default reservation duration is determined by the value specified in this field. CUE Assist automatically sets the reservation end time to match this duration. The user can still modify the reservation time before saving the reservation. ### Max. extended event duration in units** ** This field defines the maximum total duration of an event after it has been extended from the resource unit. It specifies the maximum event length, not the duration of an individual extension. For example, if an event is originally scheduled from 9:00 to 11:00 and the maximum duration is set to 2 hours 30 minutes, the event can be extended until 11:30. If another reservation starts before this limit is reached, the event can be extended only until the start of the next reservation. ### Max. advance reservation in units This field defines how far in advance a new reservation can be created directly from the resource unit. It does not limit the reservation duration, but the latest permitted start date of the reservation. The following options are available: - **Current day** – reservations can be scheduled only for the current day - **2–5 days / 1 week / 2 weeks / 1 month** – reservations can be scheduled only within the selected time period - **Ad hoc events only** – Only immediate reservations starting “now” can be created, reservations for a later time cannot be scheduled from the resource unit ## Event confirmation ![image-20260803-114226.png](media://16202c57-84e6-4896-a6b9-eb3839a7e123) ### Action for unconfirmed event This field defines the action performed when an event has not been confirmed by the configured deadline. An event is considered unconfirmed if it has not been confirmed through any of the enabled confirmation methods configured in *Confirm by* (see below), such as CUE Assist, the resource unit, or an occupancy sensor. - **Turned off** – Event confirmation is disabled for the resource. Unconfirmed reservations remain valid, and the resource stays reserved for the entire reservation period. All other event confirmation settings are disabled. - **Only record in analytics** – The reservation remains unchanged and the resource is not released. Instead, the event is recorded as unconfirmed. This information can be used in analytics, for example to evaluate how often resources are reserved but not actually used. - **Only record in analytics and send email** – The reservation remains unchanged and the resource is not released. The system records the event as unconfirmed and includes this information in analytics. After the confirmation deadline has passed, an informational email is sent to the event organizer. - **Make the resource free** – If the event is not confirmed by the configured deadline, the reservation is released automatically. For example, if the action is configured to occur 15 minutes after the event start and the event has not been confirmed by that time, the reservation is cancelled and the resource becomes available for new reservations. ### Confirm by This section defines which confirmation methods can be used for this resource. If multiple methods are enabled, confirming the event using any one of them is sufficient. The event does not have to be confirmed by all enabled methods. > ℹ️ These options are disabled when Event confirmation is set to Turned off. - **CUE Assist (QR code)** – The event is confirmed by scanning the QR code assigned to the resource. Scanning the QR code opens the corresponding event in CUE Assist, where it can be confirmed. - **Unit** – The event is confirmed using the unit assigned to the resource. - **Sensor** – The event is confirmed automatically when the occupancy sensor assigned to the resource detects the presence of people. No user interaction is required. This option requires a correctly connected and configured occupancy sensor. Enabling the option alone does not result in automatic event confirmation. **Multi day events** This field defines how often a single continuous reservation spanning multiple days must be confirmed. It does not apply to recurring reservations consisting of separate events. - **Confirm start** – A reservation needs to be confirmed only once, at the beginning of the event. If the reservation is not confirmed on the first day, the configured *[Action for unconfirmed event](https://cue.atlassian.net/wiki/spaces/TAM/pages/2756378635/Additional+Resource+Configuration#Action-for-unconfirmed-event)* is performed. If *Make resource free* is selected, the resource is released for the remainder of the reservation. - **Confirm every day** – A reservation must be confirmed again on each day of the event. If the reservation is not confirmed on a particular day, the configured *[Action for unconfirmed event](https://cue.atlassian.net/wiki/spaces/TAM/pages/2756378635/Additional+Resource+Configuration#Action-for-unconfirmed-event)* is applied for that day. If *Make resource free* is selected, only the unconfirmed part of the reservation is released. Any remaining days of the reservation are preserved and require confirmation on their respective days. ### Time for confirmation This section defines when an event can be confirmed, the confirmation deadline, and whether the event organizer receives a reminder before the deadline expires. - **Before event start time** – This field specifies how many minutes before the scheduled start of the reservation the confirmation option becomes available. > ℹ️ When confirmation is performed on the resource unit, the *Mark as occupied before event starts* setting configured in the *[Units Settings](https://cue.atlassian.net/wiki/spaces/TAM/pages/161841167)* also applies. If this value differs from the resource setting, **the lower value is used**. For example, if the resource is set to 15 minutes and the unit to 5 minutes, the confirmation option becomes available on the unit 5 minutes before the event starts. - **After event start time** – This field specifies how many minutes after the scheduled start of a standard reservation the event can still be confirmed. It does not affect the reservation start time, but only the period during which the system waits for confirmation. If the event is not confirmed by the configured deadline, the configured *[Action for unconfirmed event](https://cue.atlassian.net/wiki/spaces/TAM/pages/2756378635/Additional+Resource+Configuration#Action-for-unconfirmed-event)* is performed. - **For all day events at** – Because all-day reservations typically start at midnight, the confirmation deadline cannot be specified as a number of minutes after the reservation start. Instead, a specific time of day is used. If the reservation is not confirmed by this time, the configured *[Action for unconfirmed event](https://cue.atlassian.net/wiki/spaces/TAM/pages/2756378635/Additional+Resource+Configuration#Action-for-unconfirmed-event)* is performed. **Send warning email to organizer** When selected, a warning email is sent to the event organizer if the reservation has not yet been confirmed. - **After event start time** – This field specifies how many minutes after the scheduled start of a standard reservation the warning email is sent if the reservation is still unconfirmed. - **For all day events at** – This field specifies the time of day when the warning email is sent for all-day reservations and the corresponding days of multi day events. > ℹ️ It is recommended that the warning email be sent before the confirmation deadline to give the event organizer sufficient time to respond before the configured *[Action for unconfirmed event](https://cue.atlassian.net/wiki/spaces/TAM/pages/2756378635/Additional+Resource+Configuration#Action-for-unconfirmed-event)* is performed. **Advanced confirmation settings** This section allows different event confirmation rules to be configured based on the total reservation duration. Short, standard, and long reservations can therefore be handled differently if they are not confirmed. The advanced settings modify only the *[Action for unconfirmed event](https://cue.atlassian.net/wiki/spaces/TAM/pages/2756378635/Additional+Resource+Configuration#Action-for-unconfirmed-event)* and the confirmation mode for *Multi day events*. All other event confirmation settings are inherited from the default configuration. - **Event length less than** – This rule applies if the total reservation duration is shorter than the configured threshold. - **Event length greater than** – This rule applies if the total reservation duration exceeds the configured threshold. > ℹ️ If a reservation does not match either advanced rule, the event confirmation settings configured above are applied. The *Event length less than* threshold must not exceed the *Event length greater than* threshold. Reservations with a duration between these two thresholds always use the event confirmation settings configured above. ## Emails ![image-20260803-114520.png](media://2df99483-c667-451e-98ea-e1ae176b72bd) This section contains settings for informational emails related to the event, which can be sent to the event organizer and, if required, to the event participants. For information on customizing the email content, see [here](https://cue.atlassian.net/wiki/spaces/TAM/pages/476905929). **Send an email before the event** When selected, the system sends an informational email before the reservation starts. The *Minutes before the event* field specifies how many minutes before the scheduled start of the reservation the informational email is sent. The value can be set between 5 and 15 minutes. **Send an email before the end of the event** When selected, the system sends an informational email before the scheduled end of the reservation. The *Minutes before the end of the event* field specifies how many minutes before the scheduled end of the reservation the informational email is sent. The value can be set between 5 and 15 minutes. **Send only to organizer** When not selected, the email is sent to both the event organizer and the event participants. > ℹ️ If the corresponding email option is not selected, the associated timing and recipient settings are ignored. ## Unoccupied resource management ![image-20260803-114520.png](media://2df99483-c667-451e-98ea-e1ae176b72bd) This section defines how the system handles reservations that are still in progress even though the occupancy sensor no longer detects the presence of people. Unlike *[Event confirmation](https://cue.atlassian.net/wiki/spaces/TAM/pages/2756378635/Additional+Resource+Configuration#Event-confirmation)*, which verifies occupancy at the beginning of a reservation, these settings handle situations where the resource is vacated before the reservation ends. > ℹ️ This feature requires reliable occupancy information, typically provided by a correctly connected and configured occupancy sensor. **Action for abandoned resource** This field specifies the action performed when no occupancy is detected for the resource. **Not required** – Unoccupied resource management is disabled. The system neither ends the reservation nor sends a warning email when no occupancy is detected. The remaining settings in this section are ignored. **Cancel event** **Send email warning only** **Timetable when monitoring of abandoned resources is active** This field specifies the schedule during which the system monitors occupancy and reacts when the resource becomes unoccupied. For example, it can be configured to operate only on selected days or during specific time periods, such as regular working hours. Time schedules are configured in *Units* → *Timetables*. For instructions on how to configure them, see [here](https://cue.atlassian.net/wiki/spaces/TAM/pages/156991604). ## Panel unit behavior ![image-20260803-114520.png](media://2df99483-c667-451e-98ea-e1ae176b72bd) This section defines how the resource unit behaves when creating reservations, searching for available resources, and confirming events. **Enable private event reservation** When selected, the resource unit allows users to create both public and private reservations. When not selected, only public reservations can be created.