--- title: "Prerequisites for using CUE Assist" canonical: "https://docs.cuesystem.com/space/assist/2832924676/Prerequisites%20for%20using%20CUE%20Assist" format: markdown --- > Macro (toc) Before CUE Assist can be accessed and used correctly, several configuration steps must be completed in CUE Admin. The following sections describe the basic prerequisites required to make CUE Assist available and ensure its proper operation. ## CUE Admin registration After CUE Solution is installed, the registration screen is displayed. It is used to create the administrator account for CUE Admin. The designated administrator enters the required information: - **Reservation suite name** – pre-filled by default, but can be changed according to the customer’s preferences - **Registrator verification** – the license file provided for the CUE Solution installation is uploaded here - **Connection agent used for sending emails** – the administrator must ensure that a connection agent responsible for sending emails within CUE Solution is available. The required information depends on the selected service, such as Microsoft 365, Exchange, or Google. The fields displayed on the registration screen vary according to the selected option. > ℹ️ The connection agent for sending emails must be available during registration to ensure that the administrator can reset a forgotten CUE Admin password. Without a functioning email connection, the system cannot send the password reset email. Once the registration is successfully completed, the CUE Admin administrator account is created. ## Connection agent configuration Connection agents are configured in *CUE Admin* → *Connection* → *Connection agents*. The connection agent for sending emails specified during registration is automatically displayed in the list. Connection agents are used to connect CUE Solution to the customer’s calendar server or servers. The required configuration depends on the type of calendar server. Supported calendar servers include **Microsoft 365**, **Google**, **Exchange**, and **CUE Calendar**. Connection agent types: - **For sending emails** – handles the sending of system emails, such as reservation confirmations, user PINs, and password reset links - **For API operations** – handles automated background operations, such as retrieving and confirming reservations or processing statistics and orders - **For import resources and users** – connects CUE Solution to the customer’s calendar server and retrieves resources and users for use within the system - **For apps** – Connects CUE Admin, CUE Assist, and the Outlook Add-in to external calendar servers and enables user authentication - **For units** – allows panels and other units to access resource calendars and send emails ## Importing resources ### Synchronization of resources A full synchronization must be performed for the Connection agent for import to retrieve the available resources from the calendar server. In the list of connection agents, the Import agent must be selected and Full synchronization must be performed to retrieve the available resources from the calendar server. CUE Admin then reloads the complete list of available resources from the calendar server. > ℹ️ Note that the synchronization process retrieves **both resources and users** from the calendar server. When importing items into the resource list, it is therefore necessary to distinguish between them and ensure that only resources are imported. ### Creating resource types In *CUE Admin* → *Resources* → *Types*, the resource types required for the customer’s environment must be created, such as workplaces, offices, or meeting rooms. Instructions for creating a new resource type are available [here](https://cue.atlassian.net/wiki/spaces/TAM/pages/663584980). > ℹ️ In a new CUE Admin installation, only one resource type (Room) is available by default. Creating the relevant resource types in advance simplifies the subsequent resource import. ### Importing resources by resource type In *CUE Admin* → *Resources* → *List*, the :newimportt: button is used to import resources into the resource list. It is recommended to import resources in separate groups according to their resource type, for example, workplaces and meeting rooms separately. On the General tab, the appropriate resource type and connection agent for API operations must be selected. The import is completed by clicking the :save: button, after which the imported resources are displayed in the resource list. > ℹ️ If the resource is equipped with a reservation panel, a connection agent for units must also be selected. Working hours are retrieved from the calendar server but can be modified if necessary. Additional settings can be configured as required. Detailed information about the available settings can be found [here](https://cue.atlassian.net/wiki/spaces/TAM/pages/562757633). ## Creating areas Areas define where individual resources are physically located. In CUE Admin, it is recommended to create a simple area structure that reflects the actual layout of the customer’s environment. An area can represent a site, building, floor, or another logical part of the location. Areas are organized in a hierarchical tree structure, similar to folders on a computer. This structure allows CUE Assist to identify where resources are located, search for resources within the relevant part of a building, and provide navigation where available. If only reservation features are used and navigation is not required, a simple area structure is sufficient to begin with. Floor plans can be added later if navigation is required. > ℹ️ By default, one area is created in *Smart building* → *Areas*. More information about creating the area structure can be found [here](https://cue.atlassian.net/wiki/spaces/TAM/pages/775389214). The resources must now be assigned to the appropriate areas within the created area structure. If navigation is not used, resources can be assigned directly to the relevant area by selecting all resources located there from the list and confirming the assignment using the :save: button. More information about assigning resources to the area structure can be found [here](https://cue.atlassian.net/wiki/spaces/TAM/pages/562528309). ## Assigning licenses For resources to function correctly in CUE Assist, a Standard or Premium license must be assigned to them in *System* → *Licenses* → *Assignment*. A Standard license allows reservations to be created for a resource. With a Premium license, additional participants can also be invited to the event. A **Standard** license is therefore typically sufficient for resources such as workplaces or parking places, while a **Premium** license is recommended for meeting rooms where reservations may include multiple participants. More information about the available license types and how they are assigned to resources can be found [here](https://cue.atlassian.net/wiki/spaces/TAM/pages/777519114). ## Importing users Users are imported in the same way as resources. Since Full synchronization has already been performed, the users retrieved from the calendar server are already available in the system. In *CUE Admin* → *User management* → *Users*, the :newimportt: button displays the list of retrieved users (and resources). After the required users are selected, the selection can be confirmed directly using the :save: button; no additional configuration is required at this stage. The imported users are then displayed in the user list. ## CUE Assist feature configuration The *Application* → *Assist* section defines the functionality available in CUE Assist, including the features users can access and the actions they can perform after signing in. Depending on the selected configuration, individual features become available in the CUE Assist interface, allowing the application to be tailored to the specific requirements of the customer and its users. More information about configuring CUE Assist features can be found [here](https://cue.atlassian.net/wiki/spaces/TAM/pages/469368877).