> 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/code-security/application-security-scans-management/manage-scans-through-the-tenant-ui/pull-request-scans/references/reference-i-permissions.md).

# Reference I: Permissions

| Permission                    | Scope                                                                                                        |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------ |
| `app_sec_scans_pr_view`       | View pull request scan results                                                                               |
| `app_sec_scans_pr_edit`       | Action-level permission on the Pull Request Scans page                                                       |
| `app_sec_scans_periodic_view` | View branch periodic scan results                                                                            |
| `app_sec_scans_periodic_edit` | Trigger a rescan on a branch periodic scan                                                                   |
| `app_sec_scans_ci_cd_view`    | View CI scan results                                                                                         |
| **Data Sources (View/Edit)**  | Open and save the repository **Scan Configuration**, where **Scan PR** and **Fail PR on scan error** are set |

Access to **Scans** requires at least one scan view permission. A user holding only `app_sec_scans_pr_view` can access Pull Request Scans, but cannot view periodic or CI scan results.

Viewing scan results and enabling pull request scanning require different permissions. Scan permissions govern the inventory only. A practitioner closing a coverage gap also needs **Data Sources (View/Edit)**.

> **Note:** Pull request scans have no rescan action. Therefore, `app_sec_scans_pr_edit` does not gate a rescan as `app_sec_scans_periodic_edit` does for branch periodic scans.


---

# 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/code-security/application-security-scans-management/manage-scans-through-the-tenant-ui/pull-request-scans/references/reference-i-permissions.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.