> 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/application-security/onboard-data-sources/onboard-version-control-systems/github-cloud/reference-a-shared-cortex-github-app-permissions.md).

# Reference A: Shared Cortex GitHub App permissions

This reference lists the GitHub App permissions the shared Cortex GitHub App requests. Palo Alto Networks owns and maintains the shared Cortex GitHub App, so these permissions are fixed and cannot be modified per tenant.

| Permission               | Access | Purpose                                                                              |
| ------------------------ | ------ | ------------------------------------------------------------------------------------ |
| `actions`                | Read   | Scan GitHub Actions configurations                                                   |
| `actions_variables`      | Read   | Read repository-level Actions variables                                              |
| `administration`         | Read   | Read repository metadata, branch protection, and team access                         |
| `checks`                 | Write  | Report scan results as check runs on pull requests                                   |
| `contents`               | Write  | Read source code for scanning and commit fix pull request suggestions                |
| `deployments`            | Read   | Read deployment information for supply chain visibility                              |
| `discussions`            | Read   | Read discussions for context during scans                                            |
| `issues`                 | Write  | Create issues for scan findings                                                      |
| `metadata`               | Read   | Basic repository discovery (auto-granted)                                            |
| `packages`               | Read   | Read package information for SCA dependency analysis                                 |
| `pull_requests`          | Write  | Post scan result comments and reviews on pull requests, and create fix pull requests |
| `repository_hooks`       | Write  | Read webhook configuration for pull request scan triggers                            |
| `secrets`                | Read   | Read Actions secrets metadata for CI/CD security                                     |
| `secret_scanning_alerts` | Read   | Read secret scanning alerts                                                          |
| `security_events`        | Read   | Read code scanning (SARIF) alerts                                                    |
| `statuses`               | Write  | Set commit status checks (scan pass or fail)                                         |
| `vulnerability_alerts`   | Read   | Read Dependabot alerts for SCA enrichment                                            |


---

# 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/application-security/onboard-data-sources/onboard-version-control-systems/github-cloud/reference-a-shared-cortex-github-app-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.