> For the complete documentation index, see [llms.txt](https://docs.cw.crisisworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cw.crisisworks.com/security-and-support/releases/whats-new-in-2026.md).
# What's new in 2026
An outline of some of the key improvements Datalink has brought you in 2026
### Key benefits
🔌 Work faster and more reliably in the field
📊 Give stakeholders clearer insight with improved data extraction
🔍 Find the right data, faster
🧠 Cut down manual work with new productivity features
### New features in the new look V5
📱 **Revamped offline experience**\
Gives you more control over what syncs and when. Perfect for unpredictable network coverage.
✏️ **Save your edits as drafts on your device**\
Make updates and come back to them later before uploading.
📊 **Improved maps and search**\
Make data access faster and more intuitive.
🖼️ **Smarter image handling**\
Reduce file sizes and increase upload speeds. Configured to your needs.
🛠️ **Performance improvements**\
Make everything feel more responsive.
🪄 **Bulk Merge for Recovery Cases**\
**C**ombine records easily to reduce admin overhead.
📋 **Related Assessments**\
Instantly see associated assessments while reviewing a case.
📥 **Export Your Reports to Excel**\
Perfect for offline analysis and sharing with stakeholders.
🔄 **Querying (CQL) improvements**\
Searching is more powerful than ever.
---
# 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://docs.cw.crisisworks.com/security-and-support/releases/whats-new-in-2026.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.