> For the complete documentation index, see [llms.txt](https://operations.clausebase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://operations.clausebase.com/updates-october-2025/30-october-2025.md).
# 30 October 2025
## Doc Chat length
Improvement In Doc Chat, you can now specify a short, medium-length or long answer (previously only "concise" could be selected). Your setting will be remembered between sessions until you log out.
***
## User assets overview
New feature There's a new flyout menu that allows administrators to immediately see the number of clauses, folders and documents owned by a particular user. These ownerships can also be reassigned to another user (e.g., before the user would be deleted).
## Export users list
New feature The list of users can be exported to an Excel file that contains the first name, last name, email address, state (anonymous / disabled), groups and profiles of each user.
***
## Show owner information
Improvement The "Additional information" of a Quality Clause library now also shows the owner of a clause.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://operations.clausebase.com/updates-october-2025/30-october-2025.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 `build a script that syncs our docs to a CMS` 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.
