> For the complete documentation index, see [llms.txt](https://docs.gospace.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gospace.com/whats-new/release-notes/v2.2.1.md).

# v2.2.1

We're excited to announce the release of gospace v2.2.1. This update introduces a powerful new visualisation tool for admins, enhances privacy features, and improves the user experience with more informative upcoming cards.

### New Features and Improvements

#### 1. Stack Plan View in Admin Console

We've introduced a new stack plan visualisation in the Planning > Allocations section of the admin console. Admins can now access a comprehensive overview of team allocations across all floors with a single click of the stack plan icon. This new view instantly displays the number of spaces allocated to each team on every floor of a location for the selected day.

![](/files/VCKEmGnTlvjCcyZi31s1)

The stack plan offers a swift, visual overview of space usage, enabling administrators to optimise allocations and grasp team distribution throughout the building. It displays floor numbers on the left axis and capacity on the bottom axis, with colour-coded bars representing different teams. When hovering over a team's allocation on a specific floor, detailed information about the number of spaces allocated to that team is revealed.

#### 2. Enhanced Privacy Preferences

We've enhanced the system's handling of user privacy settings. When a user activates the "Schedule hidden" option, other users (except Executive Assistants and Schedule Managers) will now see a clear message indicating that the schedule is hidden. This replaces the previous behaviour where just an empty schedule was displayed, making it less confusing to a user then thinking the person has nothing scheduled.

#### 3. Improved Upcoming Cards

We've enhanced the information displayed on scheduling cards in the user app. Both the upcoming cards and today cards now show the number of confirmed invitees via an icon. This addition provides users with at-a-glance information about how many people are confirmed for a particular scheduled event or space.

Previously, just the today cards had these icons.

### Coming Soon

* Ability to edit an intention for a future or same day <mark style="color:green;">(in pre-release testing)</mark>
* Priority location mapping from the integration to sync with waitlist, ensuring priority is given to those with a priority location  <mark style="color:green;">(in pre-release testing)</mark>
* AIDRA metrics MVP on planning <mark style="color:orange;">(issue identified: in late stages of QA testing)</mark>
* Shifts for room scheduling <mark style="color:green;">(in pre-release testing)</mark>
* Shifts for space scheduling <mark style="color:orange;">(in late stages of QA testing)</mark>

Thank you for your continued trust and support in gospace. If you have any questions about these new features or encounter any issues, please don't hesitate to reach out to our support team.

* The gospace Team


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.gospace.com/whats-new/release-notes/v2.2.1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.