> For the complete documentation index, see [llms.txt](https://support.meetuma.ai/uma-knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.meetuma.ai/uma-knowledgebase/release-notes/web/2024/v3.1.1-3rd-december-2024.md).

# v3.1.1 - 3rd December 2024

## Visitor management improvements

### **Hide visitor details in emails**

* **New setting:**\
  Admins can now utilise the new **‘Hide Visitors in Emails’** setting, available in the **Visitor Management** section of **Company** or **Building Settings**.
* **Setting:**
  * The setting is defaulted to **OFF**.
  * When enabled, a **BCC rule** will enforce the hiding of visitor names and emails from all visit-related emails/events.
* **Applies to:**
  * Visit emails triggered during **creation**, **updates**, or **cancellations** of visits.
  * Supported integrations include **UMA Calendar**, **Microsoft Calendar**, and **Google Calendar**.
  * Works seamlessly for calendar event-based notifications as well as standard email notifications.

### **All buildings filter**

* Users across all roles can now select an **‘All Buildings’** filter on the **Visitors page**, enabling the ability to view visit data across multiple buildings in one consolidated view.

### **Export enhancements**

* **For Admin and Advanced Manager roles:**
  * The **‘Export all to CSV’** and **‘Emergency Report’ CSV** now include new columns:
    * **‘Visitor Email Address’**: Provides the email address of the visitor for better reporting and management.
    * **'Building'**: Displays the building associated with each visit, enabling easier identification and filtering of visit data.

***

## **Occupancy sensor data on the Office Map Application**

* **Feature overview:**\
  Users can now view **occupancy sensor data** directly within the **‘Desks and Rooms’** view of the Office Map.
* **Details:**
  * Occupancy sensors assigned to resources (desks and rooms) will display their real-time status, similar to the **‘My Floor’** map page.
  * This provides greater visibility into the availability and usage of office resources, helping teams optimise workspace utilisation.

***

## **Recurring meeting improvements**

### **Meeting room availability check for recurring meetings**

* **Informed booking process:**\
  When setting up a recurring meeting, users will now be notified if the selected meeting room is unavailable for any event in the series.
* If the room is busy for one or more events, a notification message will display highlighting the event clashes.

We’ve addressed important issues related to **recurring room bookings** and their adherence to neighbourhood and booking threshold policies. These updates ensure compliance with configured policies and improve the user experience.

### **Fix: Neighbourhood and Teams policies for recurring room bookings**

**Issue overview**

* **Problem:**\
  Recurring room bookings did not respect neighbourhood or team policies. For example:
  * If policies disallowed bookings on specific days (e.g., Wednesdays), users could still book a recurring meeting that included those days.
* **Resolution:**
  * Recurring bookings now adhere to neighbourhood and team policies.
  * Days that are restricted by policies will be **greyed out** on the date picker, preventing users from selecting them for recurring bookings.

### **Fix: Room Booking Threshold policies for recurring room bookings**

**Issue overview**

* **Problem:**\
  Recurring room bookings bypassed company or building **Room Booking Threshold** policies. For example:
  * If a threshold limited bookings to 4 days, users could still book recurring meetings exceeding this limit (e.g., 6 days).
* **Resolution:**
  * Recurring bookings now comply with room booking thresholds set in company or building settings.
  * **Greyed-out dates** will now appear in the date picker for dates beyond the allowed threshold, similar to standard bookings.

***

## **Default resource type for Calendar View**

**What’s new?**

* The **‘Room’** resource type is now set as the **default selection** in the **Calendar View**.
  * Users will automatically see room bookings displayed when accessing the Calendar View, streamlining the experience for those primarily managing room resources.

**Why this update?**

* Simplifies navigation for users who predominantly manage room resources.
* Reduces the need to manually switch resource types, saving time and enhancing efficiency.

***

## Milesight VS121 line crossing counting support

We have now added support to count people within a space using the Milesight VS121 line cross mode.

***

## **Fixes and improvements**

1. **Edit/Cancel desk bookings:**
   * Users can now edit or cancel desk bookings even after they’ve been checked in.
2. **Room count by capacity chart:**
   * The chart now resizes correctly, even when displaying a large number of rooms with varying capacities.
3. **Capacity filters in calendar and map views:**
   * Previously, setting a capacity filter in the **Calendar View** and switching to the **Map View** retained the filter incorrectly. This has been fixed, and the capacity filter is now removed when transitioning to the Map View.
4. **Recurring booking start date update:**
   * Changing weekly or monthly recurrence settings now automatically updates the start date for the booking.
5. **Admin and Advanced Manager permissions:**
   * Admins and Advanced Managers can now edit or cancel meetings that were automatically booked by the meeting room itself.
6. **Quick book resource availability issue:**
   * The **Quick Book** feature on the **My Floor page** was including seconds in bookings, which caused issues with displaying resource availability. This issue has been resolved.
7. **Time picker rounding issues:**
   * Fixed rounding issues in time pickers across all resource types to ensure accurate time selection.
