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

# Version 1.11.0

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

#### 1. New Features

1. New photo and video editor with annotation, text, crop and video trim tools
2. Richer forms with checkboxes, an Other option, attachments, signatures and PDF templates
3. Remove forms posted in a discussion and include completed form answers in PDF exports
4. Archive and restore forms and other module resources in the admin app
5. Authorized administrators can validate members' professions

#### 2. Improvements

1. Form and trajectory updates arrive without restarting the app
2. More reliable recovery of interrupted uploads
3. Better screen reader support and more accessible navigation
4. Clearer admin configuration and a new Support menu

#### 3. Fixes

1. More reliable patient record saving, identifier handling and numeric form answers
2. Fixed closed-discussion synchronization and notifications sent before a discussion was accepted
3. Corrected availability times on iOS and email removal actions
4. More reliable account creation and invitation-based sign-in, while preserving existing sessions
5. Fixed module selection, field ordering and audit-log pagination in the admin app


---

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