> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/releases/2025/2025.21.0-october-29-2025-preview-release.md).

# 2025.21.0 - October 29 2025 Preview Release

Changes are scheduled to go to production on November 12 2025

## Improvements & Bug Fixes

* Removed the platform Analytics Dashboard from the UI. The data presented there was inaccurate and misleading for our customers, so we are disabling access to it for the time being while we work on improving the data accuracy.
* Improved the initial load of the platform UI for users who are members of larger sets of orgs. If you're only a member of a couple or handful of orgs, you may not notice any significant difference. The UI was previously loading information about every org that was available to the login user, thus slowing down the initial platform UI load until that step was completed.


---

# 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://community.threekit.com/releases/2025/2025.21.0-october-29-2025-preview-release.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.
