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

# v2.0.3

## User app early access release

With this release we are sharing an early access version of the user app. This early access version has some in progress features, and a few bugs. These bugs are due to data not correctly replicating through the full end to end system, therefore should be resolved shortly.

With this release we have also done further quality of life and functional fixes to the admin console. Furthermore we are releasing the floorplan functionality to the devices URL, meaning now via devices you can view if a room has a meeting, quick book, or configure the device to work as a floorplan monitor, showing all the allocations of that floor on the current day.

To access the floorplan monitor register your device via the admin console, then view allocations for the configured floor at: <https://device.sandbox.gospace.app/auth/login>

<figure><img src="https://2315052346-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOW0EmyC5IqyMiB4AxcLq%2Fuploads%2FXERJIjdb9w2SKrDjkju9%2FIMG_0054.jpeg?alt=media&amp;token=f9027a1f-576a-493a-b547-5a4e8aa02369" alt="" width="375"><figcaption></figcaption></figure>

### Fixed:

* Priority Locations Assigned Incorrectly to All Users
* Duplicate Email Address Allowed During Person Edit
* Multiple Redundant Records Created During Occupancy Data Sync in SFTP or Snowflake Integrations
* Teams Created via SFTP Import Are Empty Despite Available People Data
* Duplicated Teams After Initial Sync in Integrations
* In the console, when allocating for a specific date, the allocations are incorrectly applied to the next day instead of the intended current day.&#x20;
* Allocations show undefined in allocations page in the console.
* Snowflake Integration Fails to Update Team Changes for Individuals
* Incorrect Team Mapping Due to Row Duplication in Snowflake Integration
* If a user is edited (not master), the changes are not shown when viewing a team containing the edited user.
* Error Occurs When Setting Default Team Created by Integration
* Users Cannot Log In After Being Assigned Admin User Role<br>

### Still in progress:

* Ability to schedule meeting rooms
* Ability to schedule team rooms

### Known issues:

* Some floorplans have issues with allocations not showing <mark style="color:orange;">(In Progress)</mark>
* Changes Not Reflected When Creating Space Settings for Fixed Teams <mark style="color:orange;">(In Progress)</mark>
* When entity is deleted it is not removed from user's defaults <mark style="color:orange;">(In Progress)</mark>
* Schedule space for the another user of the same team on the same day hangs on "finding your space" <mark style="color:orange;">(In Progress)</mark>
* Able to Schedule for Dates When Building is Closed <mark style="color:orange;">(In Progress)</mark>
* AIDRA replication can cause issues where some corrupted intentions have been created <mark style="color:orange;">(In Progress)</mark>
* Teams selector is still showing ALL teams when setting your team in default team or scheduling with a team <mark style="color:orange;">(In Progress)</mark>
* Capacity tracker can sometimes cause 500 when trying to schedule, if this does occur, wait until a full hour, or half hour, i.e. 3:30 or 4pm for the capacity tracker to re-run and see if the issue is resolved. <mark style="color:green;">(Under investigation for further improvement)</mark>

For early access to the user app please use your sandbox console login and access via: <https://app.sandbox.gospace.app/auth/login>

For any queries please reach out, and report any issues via the current issue tracker on JIRA.


---

# 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.0.3.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.