> 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.6.0.md). # 2026.6.0 **Upgrade Notes** To upgrade to AppControl 2026.6 follow these steps: 1. Upload the AppControl release package to your Mendix Cloud environment. 2. Disable the following scheduled events: 1. Core.SCE\_process\_models 2. Policies.SCE\_check\_all\_apps 3. Deploy the package to your AppControl environment. (Note: We recommend that you first deploy to your ACC environment to test the upgrade) 4. After deploying the new AppControl package (and restarting the environment), go to **Administration > System Logs / Tools > Background Jobs**. Filter this view on the the job type 'System' and the text '2026.6' in the Message column. The upgrade will execute in the background and will update the storage format of all data policies. Wait for it to complete. Depending on the size of your environment it can take from 30-120 minutes to complete. 5. After the upgrade has completed, re-enable the scheduled events that you disabled in step #2 above. Restart the environment. {% hint style="info" %} This release of AppControl involves a significant upgrade to our used Mendix components: Mendix 11 LTS, Atlas 4, the Mendix React Client, and the integration of GenAI. Although we have spent a lot of time testing the entire UI, there may still be issues. We appreciate your patience as we make the platform on which AppControl is developed ready for years to come. {% endhint %} *** **New Features** \[CORE] Support OAuth 2.0 for Notifications. Notifications can now be configured to authenticate using OAuth 2.0, giving you a more secure and modern authentication option than static credentials. \[CORE] Support digital signing and encryption of emails. Outgoing emails can now be digitally signed and encrypted, helping protect sensitive content in transit and supporting compliance with data protection requirements. \[POLICIES] Auto-detect personal data and data classification level. AI-based detection now identifies personal data and suggests the corresponding classification level, speeding up data policy setup and improving consistency across apps. \[POLICIES] Auto-detect excessive privileges. AppControl now automatically flags user roles that have excessive privileges, helping you spot and remediate access risks before they become compliance issues. \[POLICIES] Auto-detect user role types in Data Policy. User roles are now automatically classified as User or Admin roles, reducing the manual work needed to configure user role governance. \[CORE] Add OIDC as supported authentication service. OpenID Connect (OIDC) is now available as an authentication method, giving you a modern, widely supported alternative now that Mendix SSO has been removed. \[POLICIES] App Owners should be able to manage app access. App Owners can now manage access to their own apps directly, reducing the need to route access requests through platform administrators. \[CORE] View app group membership in App Info page. The App Info page now shows which app groups an app belongs to, making it easier to understand how policies and access are inherited for that app. \[INSIGHTS] View data classification records in Insights. Data classification records are now available in Insights, giving you a single place to report on and audit how data is classified across your portfolio. \[POLICIES] Add POLICY\_CHANGED audit event. A new audit event is logged whenever a policy is changed, improving traceability for compliance and audit purposes. \[TASKS] Delete accounts that have completed a task. Accounts that have completed a task can now be deleted, making it easier to keep your account list clean and up to date. *** **Improvements** \[CORE] Upgrade to Mendix 11 LTS. AppControl has been upgraded to run on the Mendix 11 Long-Term Support release, ensuring continued security updates and platform stability for years to come. \[CORE] Mendix 11: Upgrade to Mendix React Client. AppControl now runs on the Mendix React Client, providing a more modern and performant UI foundation than the deprecated Dojo-based client. \[CORE] LTS Update: Replace Any Charts with Charts widget. The deprecated Any Charts widget has been replaced with the native Charts widget as part of the Mendix 11 upgrade, ensuring charts continue to render correctly going forward. \[CORE] Remove Mendix SSO as supported authentication service. Mendix SSO has been removed as a supported authentication method following its deprecation by Mendix, with OIDC now available as the recommended replacement. \[UX & SUPPORT] UI refresh. The interface has been refreshed across the platform for improved compactness and visual consistency, making it easier to navigate and scan information at a glance. \[CORE] Add additional safety mechanism to prevent repository out of sync condition. An additional safeguard has been added to prevent the repository from becoming out of sync, reducing the risk of inconsistent data between AppControl and and the central Blue Storm repository. *** **Resolved Issues** \[RELEASES] Task scheduling is not working when first task has a scheduled date. Fixed an issue where task scheduling failed when the first task in a release had a scheduled date. \[POLICIES] Link to COMP\_0001 online docs can't be found. Fixed a broken link to the COMP\_0001 online documentation. --- # 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.bluestorm.io/support/releases/appcontrol-2026/2026.6.0.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.