> For the complete documentation index, see [llms.txt](https://support-en.braver.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support-en.braver.net/changelog/1.10/version-1.10.0.md). # Version 1.10.0 This version has been available in app stores since September 4 2026 on iOS and the web. The Android release is still pending. #### 1. New Features 1. Fill out and sign care forms directly in the app, on mobile and on the web 2. New trajectory management role, to create care channels and assign people to them without gaining access to the private content exchanged inside 3. Control what each participant or team is allowed to do in a channel, from a new restrictions panel in the inbox menu 4. Richer PDF exports, with activities, current participant status, reactions, and a clear distinction between caregivers and clinicians #### 2. Improvements 1. Lighter PDF exports for caregivers 2. Faster participant selection when adding someone to a discussion 3. Better screen reader support in text fields #### 3. Fixes 1. Care channels: fixed adding team participants during creation, a blank details screen, and restrictions that were not applied to patients on Braver Connect 2. Discussions: fixed removed users staying assignable, missing accept and decline actions for invited clinicians, and drafts that were not saved 3. PDF exports for patients now show the latest revisions instead of the original message content 4. Calls and media: fixed ending a meeting for all participants on LeoMed calls, and a crash when opening the media editor on iOS 5. Signing in: fixed Microsoft SSO account creation failing on the first attempt, and the QR code login asking for a PIN twice --- # 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-en.braver.net/changelog/1.10/version-1.10.0.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.