> 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/application-security/software-supply-chain-security/risk-and-remediation/malicious-packages/reference-b-rbac-permission-levels-by-capability.md).

# Reference B: RBAC permission levels by capability

| Capability              | Documented action                                                   | Required access        |
| ----------------------- | ------------------------------------------------------------------- | ---------------------- |
| Findings                | View malicious package findings                                     | View (read)            |
| Issues — review         | View malicious package issues; prioritize by Urgency                | View (read)            |
| Issues — backlog status | Change an issue Backlog Status                                      | View/Edit (read/write) |
| Assets                  | Filter assets by Is Malicious or the Malicious Code tab             | View (read)            |
| Dashboards              | View dashboard widgets                                              | View (read)            |
| Scan management         | Review malicious packages per scan                                  | View (read)            |
| Policies                | Create, configure, or enable and disable malicious package policies | View/Edit (read/write) |
| Public API              | Check or query packages for malicious status                        | View (read)            |

Grant view/edit on Policies and on Issue backlog status only to users who govern or triage malicious packages. Review-only users need view access on Findings, Issues, Assets, Dashboards, and Scan management.


---

# 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://cortex-docs.paloaltonetworks.com/application-security/software-supply-chain-security/risk-and-remediation/malicious-packages/reference-b-rbac-permission-levels-by-capability.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.