> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/product-updates/2026/january-2026.md).

# January 2026

*This month, we're rolling out smarter editing and new controls for BYO missions—so you can move faster and clean up less.*

## What's new?

* **Dscout + HeyMarvin integration**

  After running a study in Dscout, you can now export your entries’ CSV and media files and [import them directly into HeyMarvin](https://help.dscout.com/hc/en-us/articles/42069681362580). From there, analyze, tag, organize, and store your research alongside your other insights.

  ![](https://content.gitbook.com/content/wiBgwLWKwWLRYLRUhxPD/blobs/0InqH3Cj9rL4lL9z3Z9g/45267000323988)
* **Study templates**

  [Study templates](https://help.dscout.com/hc/en-us/articles/45017376175636) help you launch research faster and more consistently. Save any fully configured study, including mission settings, recruitment criteria, screener questions, question types, answer options, device requirements, and more, as a reusable template for future work.

  ![](https://content.gitbook.com/content/wiBgwLWKwWLRYLRUhxPD/blobs/bQY2CMB1F2EVbsX01KDE/45267000324372)
* **Control participation when recruiting your own audience**

  Set participant limits for [usability tests](https://help.dscout.com/hc/en-us/articles/42574023099156) and [media surveys](https://help.dscout.com/hc/en-us/articles/42678648668948) when recruiting via bring your own (BYO) participants. Once the limit is reached, the study automatically closes, and new participants can’t join via the share link.

  ![](https://content.gitbook.com/content/wiBgwLWKwWLRYLRUhxPD/blobs/MeKGB7CHMHsf09ZkY8u4/45267000324756)


---

# 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://help.dscout.com/product-updates/2026/january-2026.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.