> 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-c-feature-permission-requirements.md).

# Reference C: Feature permission requirements

This reference lists the three feature groups that Cortex Cloud evaluates against a Customer Owned GitHub App permissions, and the permission each feature group requires. When a Customer Owned GitHub App is missing a listed permission, or holds a permission at a level lower than required, Cortex Cloud raises a warning for that feature group on the integration status — refer to Refer to [Verify and manage VCS integrations.](/application-security/application-security/onboard-data-sources/onboard-version-control-systems/github-cloud/post-onboarding-management-and-verification.md#update-customer-owned-github-app-permissions-or-resolve-integration-errors). A `write` permission satisfies a requirement for `read` or `write`; a `read` permission satisfies only a `read` requirement.

| Feature group         | Required permissions                      | Impact when missing or insufficient                                                                                             |
| --------------------- | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| **Periodic Scans**    | `contents: read`, `metadata: read`        | Repository code cannot be read and periodic scans fail                                                                          |
| **PR Scans**          | `contents: read`, `pull_requests: read`   | Pull request code changes cannot be read and pull request scans fail                                                            |
| **Automatic Fix PRs** | `contents: write`, `pull_requests: write` | Automatic fix pull requests cannot be created. This is the same permission gate applied to the **Open Fix Pull Request** action |

NOTE: The feature permission requirements apply only to Customer Owned GitHub App integrations. The shared Cortex GitHub App holds the required permissions and is not evaluated against these feature groups.


---

# 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-c-feature-permission-requirements.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.