> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-agentix-rn/features-introduced-in-this-release/july-2026/changed-features.md).

# Changed Features

These features have been modified or removed in this release.

| FEATURE                                                 | DESCRIPTION                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
| ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Secure administrator role changes                       | Previously, non-admin users with **Access Management** permissions could grant an effective **Instance Administrator** role to users and user groups, modify access for these entities, or delete associated API keys. Now, they are restricted from doing so.                                                                                                                                                                                                                                                                                                      |
| XQL queries for cases and issues                        | Cortex Query Language (XQL) queries now strictly enforce domain-based access controls for Cases and Issues, bringing search results into closer alignment with the data visible on your user interface dashboards.                                                                                                                                                                                                                                                                                                                                                  |
| Unified support case creation via the Help Center Agent | <p>To maximize operational efficiency and reduce resolution times, clicking <strong>Initiate Support Request</strong> from the Help button now routes you directly to the Help Center Agent. This single path ensures a cohesive support experience as the agent gathers essential context and automatically attaches the chat history and conversation ID to your final support case.</p><p>If the Cortex AgentiX Assistant is not enabled for your account or available in your region, you will automatically route through the standard case creation flow.</p> |


---

# 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://cortex-docs.paloaltonetworks.com/cortex-agentix-rn/features-introduced-in-this-release/july-2026/changed-features.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.