> 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/2021/v1.6.0-13th-may-2021.md). # V1.6.0 - 13th May 2021 **Company with No Calendar** A company can now use UMA without connecting their O365 calendar. Due to customer demand we have provided the option to quickly sign in and use the application with minimal sign up process. Using UMA with no calendar will allow companies to add different sensors to the platform and view occupancy and environmental data in a variety of dashboard charts. It will also allow companies to use UMA for device and asset management purposes for monitoring AV/VC or IT hardware. **Sign In Page Update** We have updated our sign in page to provide a brand-less solution to allow for different companies with different branding options and styles. The new sign in page has been given a plain but stylish theme with scrolling images of different buildings. **Resource Description** A 'Resource Description' field has been added to the Resource entity. This will allow admins to provide useful information to users about what's included in a resource to help with the booking process. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://support.meetuma.ai/uma-knowledgebase/release-notes/web/2021/v1.6.0-13th-may-2021.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.