PURPOSE:
--------

The purpose of this module is designed to streamline the management of meeting
rooms within organizations. The significance of this module arises from the need
to efficiently allocate and utilize meeting spaces, which are vital for various
business activities.

SPECIFICATION:
--------------

## Backend:

 ### Room Configuration:

In the backend, the "Rooms" module offers comprehensive room management
capabilities. When creating a room, room managers can input essential details
such as the room name, available amenities, and associate it with a specific
company and office. Each room is provided with a dedicated URL for frontend
access, and room managers can customize this URL that includes a unique access
code. Additionally, room images for frontend representation and the ability to
set colors for the room's website are integral features.

Rooms view is facilitated through both Kanban and list views, offering efficient
management options. The kanban view provides quick insights into room
availability, displaying whether a room is currently in use or available, along
with the start time of the next meeting if available.

A convenient search panel allows users to filter rooms based on company name and
office name.

### Meeting Scheduling:

The backend functionalities of the module extend to meeting management, ensuring
seamless scheduling, updates, and removal of meetings. Various views, including
Gantt view, kanban view, calendar view, and list view, are available for
efficient meeting management. When scheduling meetings from the backend, users
are required to provide essential information such as the meeting title,
organizer's name, start time, and end time.

Moreover, the module incorporates a chatter feature within the form view of
meetings. This chatter function tracks critical meeting details, including the
meeting's start and end times, and any changes made to the organizer's name.
This feature enhances transparency and provides an audit trail for meeting-
-related activities.

## Frontend:

### Current rooms status

The frontend view is intended to be used on a static device (such as a tablet)
next to the corresponding room. It shows the current time and the availability
of the room. If the room is busy, it additionally displays the remaining time
for the current meeting. it also shows all the upcoming meetings in the
sidebar.

### Quick Schedule Meetings:

Users can quickly schedule meetings from the frontend with minimal input. They
can book the room for the next 15, 30, and 60 minutes if the room is available.

### Future Schedule:

Users can also schedule meetings that will start later. The scheduling process
begins by selecting the desired date for the meeting. Users can then select the
start and end time slots for the meeting.

### Edit Meetings:

Users have the option to reschedule or delete meetings as needed.

Users can edit meetings by clicking on them in the sidebar. In that case the
user can change the start and end dates as well as the name. They can also
delete a meeting by clicking on the fa-close icon of the booking card in the
sidebar.

TECHNICAL SPECIFICATION:
----------------------------

## Models

### room_booking model:

This model is dedicated to managing bookings. It includes fields for titles,
start times, end times, organizers, and potentially other relevant
meeting-related information.

### room_room model:

The room_room model is designed for the management of rooms. It contains fields
such as name, amenities, office, room background image, and colors for the
frontend view.

In order for the frontend view to be updated in real time, the model sends
messages through the bus service (create/delete/update bookings, update the
room).

### room_office model:

This model represents offices within a company.

## Access Rights

Members of the "Room Manager" group possess comprehensive access rights. They are
granted the ability to: create, update, and delete rooms.

Internal users can create, update, and delete every booking.

Public users can access the frontend view using the url of the room (that contains
a unique short code). They can read, create, update and delete the bookings of a
room through a controller, provided that they have the access token for the room.
This access token is used when making requests from the frontend view.

Task-3414166

PURPOSE

Visitor management helps an organization keep track of the people who
visit their location. A visitor management system makes the check-in process
painless. When guests sign in, your digital visitor log updates in real-time.
Monitor it daily, or know it's there when you need it. For instance, once the
visitor enters the organization, the digital check-in system boosts the
visitor's confidence and well-being by providing a guide and ready directions,
building on the professional first impression.

SPECIFICATION

Backend

Station Configuration:

In the backend, the "Frondesk" module offers comprehensive station management
capabilities. When creating a station, administrator can input essential
details such as the station name, set the responsibles for the station, and add
the description to show on the frontend. Each station is provided with a
dedicated URL for frontend access, including a unique secret key. Additionally,
station image and the ability to set the theme for frontend representation are
integral features.

Also, administrator and station responsible can configure various options like:
host selection - which allows the visitor to pick the host.
drink options - allows the visitor to select a drink during registration.
self-check-in - which shows a QR code on the screen to check in from mobile.
authentify guest - request additional information upon registering.
notifications - The host and station responsible will receive a notification
when a visitor registers.

Station view is facilitated through both Kanban and list views, offering
efficient management options. The kanban view provides quick insights into
displaying the number of planned visitors, visitors on site, drinks to serve,
along with the time of the latest check-in visitor.

Visitor:

The backend functionalities of the module extend to visitor management, ensuring
seamless creation, updates, and removal of visitors. Various views, including
Gantt view, kanban view, calendar view, pivot view, graph view, and list view
are available for efficient visitor management.

Additionally, administrator and responsible of the station can create planned
visitors from the backend, which helps the visitors to quick check in from the
frontend.

Frontend

Visitor Check-In:

Desk managers can efficiently check in visitors through the frontend, ensuring a
seamless process. During the registration process, the frontend offers a
selection of drinks for visitors to choose from, enhancing their overall
experience.

QR Code Check-In:

Visitors can speed up the check-in process by using QR codes displayed on the
Welcome Screen, significantly reducing wait times.

Quick Sign-In:

If a visitor has been pre-registered from the backend with a scheduled check-in
time. This innovative feature ensures efficiency by presenting planned visitors
approximately 45 minutes before and after their designated check-in time.
Whether visitors arrive early or late, the "Quick Sign-In" panel offers a
seamless check-in experience, minimizing wait times and enhancing overall
visitor satisfaction.

TECHNICAL SPECIFICATION

Models

frontdesk_frontdesk model:

The model is dedicated to managing stations. It likely contains fields such as
station names, station responsibles, messages to show on the frontend, options
like host selection - which allows the visitor to pick the host, drink options -
allows the visitor to select a drink during registration, self-check-in - which
shows a QR code on the screen to check in from mobile, authentify guest -
request additional information upon registering, notifications - The host and
station responsible will receive a notification when a visitor registers, theme
and image information for the frontdesk website.

frontdesk_visitor model:

The frontdesk_visitor model is designed for the management of visitors. It
likely contains fields such as visitor name, phone number, email, company,
check-in and check-out time, duration, station, drinks, host, message for the
visitor and visitor's status.

frontdesk_drink model:

This model represents drinks that can be configured from the station. It
contains fields like name, image, sequence, and people to notify - It will
notify the people once a visitor selects a drink.

Access Rights

In security, we have 2 groups.

Administrator Group:

Members of the "Administrator" group possess comprehensive access rights. They
are granted the ability to: Create, update, and delete stations, visitors as
well as drinks.

User Group:

The "User" group, on the other hand, has more limited permissions.

Members of this group are configured with the following access rights:
Read and update rights for the station for which they are responsible.
We are allowing user groups to create, read, and update rights for their
visitors.

Task-3381939

Co-authored-by: Earth Patel <eapa@odoo.com>
Co-authored-by: Shaan Thakkar <thsh@odoo.com>
Co-authored-by: Ipsita Borisagar <ibo@odoo.com>