> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/support/releases/appcontrol-2026/2026.4.0.md).

# 2026.4.0

***

**Upgrade Notes**

No upgrade steps are required for this release.

***

**New Features**

\[Core] App Management API — Apps can now be added to AppControl via the management API before they are auto-detected, allowing early assignment to groups and users.

***

**Improvements**

\[Core] Enhanced Java library identification — AppControl now reads manifest files to more accurately detect Java libraries and their versions.

\[Core] Incremental model processing — The model processing engine now processes only changed components, improving processing times by 25–50% depending on the size and nature of the change.

\[Policies] Policy Viewer role consolidation — The Policy Viewer and Insights Viewer roles have been merged into a single Policy Viewer role, simplifying role management.

\[UX & Support] Support conversation visibility — Users can now view their support conversation thread directly within AppControl.

***

**Resolved Issues**

\[Core] Repository enumeration defaults — Default values are now created for all repository enumeration imports, preventing missing value errors on import.

\[Policies] App Administrator role auto-assignment — Fixed an oversight where Policy Viewer users were incorrectly receiving the App Administrator role in certain cases.

\[Policies] User role type not saved in Data Policy — The selected user role type in the Data Policy module is now correctly persisted after processing a model.

\[Policies] User role type dropdown visibility — The user role type dropdown in Data Policy is now correctly visible in all cases.

***


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bluestorm.io/support/releases/appcontrol-2026/2026.4.0.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
