> 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.1.0.md).

# v2.1.0

We're excited to announce the release of gospace v2.1.0. This update introduces an enhancement to our scheduling system, designed to streamline the booking process and improve user experience.

## New Feature: Default Workspace Type Setting

We're introducing a small bug impactful new feature that allows users to set their default type. This enhancement is particularly beneficial for organisations with locations that primarily use one type of workspace, such as those mainly booking rooms or open spaces.

<figure><img src="https://2315052346-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOW0EmyC5IqyMiB4AxcLq%2Fuploads%2FxnCWsm6cZwDNiRUK6XJz%2FScreenshot%202024-09-06%20at%2018.59.48.png?alt=media&amp;token=9863ceda-81bf-4644-a9e8-74f11c17606e" alt="" width="375"><figcaption></figcaption></figure>

With this update, users can now set their preferred default workspace type (either 'Space' or 'Room') in their schedule settings, an admin can also change or set a users defaults via their profile in the admin console.

&#x20;When a user schedules for a specific date, the system will automatically populate the type field with their chosen default. This can reduce the number of clicks required to book a workspace, especially for users who consistently book the same type.

For example, if a user primarily books rooms, they can set their default type to 'Room'. Now, every time they schedule a workspace, 'Room' will be pre-selected, eliminating the need to manually change from 'Space' to 'Room' for each booking.

We've also integrated this feature with our fixed days functionality. When setting up fixed days, the system will use the user's default type from their schedule settings. However, we've maintained flexibility by allowing users to override this default on a per-day basis in their fixed day settings. This means you can have a general preference for spaces, but still easily book rooms on specific fixed days if needed.

If a user hasn't set a default type in their schedule settings, the system will default to 'Space' to maintain consistency with our previous behaviour.

This feature was developed in response to feedback from our users, particularly those in organisations where one type of workspace booking is predominant. We will further this functionality to allow default types to be automatically set, and also to be used by forecasting, so we can also forecast room intentions.

## Known Issues&#x20;

* Devices app logging out when being updated
* Default type in fixed days isn't populating the type
* Fixed days not creating intentions for a second or more configuration

## 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:orange;">(in late stages of QA testing)</mark>
* AIDRA metrics MVP on planning <mark style="color:green;">(in pre-release 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>

We're constantly working to improve your experience with gospace.&#x20;

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

&#x20;\- 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.1.0.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.