# Requirements

**Some resources are shared and are automatically created during the initial installation phase of Intranet AI (and therefore do not specifically depend on the component)**.<br>

**Below are only the resources actually used by the Booker component:**

* **App Service Plan**\
  Windows-based, created by default with the S1 pricing tier.
* **Application Insights**\
  Used for backend application logs.
* **Azure Cosmos DB Account**\
  Hosts a container with backend configurations for Intranet AI components (including Booker).\
  Estimated cost: approximately $24/month.
* **Log Analytics Workspace**\
  Workspace used by Application Insights.
* **Storage Account**\
  Hosts the JavaScript files for the web parts of Intranet AI components (including Booker).

&#x20;

**When installing the component, the following additional resources are automatically created:**

* **App Service**\
  Web application that provides the backend functionality required by the component.\
  It does not incur specific costs as it relies on the App Service Plan listed among the shared resources.
* **Dedicated Container on Azure Cosmos DB Account**

  Contains all the metadata related to the component, entered by the application itself:

  * Types of bookable entities
  * Bookable entities
  * Properties assignable to bookable entities
  * Reservations\
    \
    **Estimated cost: approximately $24/month.**

### Roles Definition

To proceed with configuring the component, it is important to clearly define roles, **specifying who will manage bookings and who will only be able to make a booking**. This ensures that, during the installation of the web part, we can assign the necessary permissions to specific users.

**Admin users can:**

* View all bookings
* Edit and create new resources
* Delete or modify any booking

**Power Readers can:**

* View all users' bookings but CANNOT modify them

**Users:**

* A basic user can only make a booking and view their own bookings on the dedicated page.