> 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.11/version-1.11.1.md).

# Version 1.11.1

This release is being prepared. Availability dates for iOS, Android and the web are still to be confirmed.

#### 1. New Features

1. You can join a Braver Connect call in your phone's browser without installing the app

#### 2. Improvements

1. In the clinician app, view and edit photos and videos while they upload
2. File transfers run more smoothly
3. The default thread title is now optional in thread templates
4. Forms show accepted formats and size limits before an attachment is added
5. Returning from a sub-form restores your place
6. On Android, PDF forms are easier to fill out with the keyboard and date picker

#### 3. Fixes

1. Trajectory filters account for your care channel access rights
2. Management-only roles apply as soon as a care channel is created
3. Quebec health insurance numbers and long identifiers display correctly in patient records
4. Form choices show their full text
5. Fields for attaching multiple files display correctly
6. Submitted PDF forms include the last entered answer
7. After sharing a form to a new thread, you stay on the page you were on


---

# 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.11/version-1.11.1.md?ask=<question>&goal=<user_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.