> For the complete documentation index, see [llms.txt](https://docs.p0.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.p0.dev/integrations/resource-integrations/github/requesting-access.md).

# Requesting GitHub access

### Requesting from Slack <a href="#requesting-from-slack" id="requesting-from-slack"></a>

Open up the p0 request modal by typing the command `/p0 request` in any Slack channel and select GitHub as the resource.

Under **Team**, start typing the name of the team you would like to be added to. As you type, suggestions will appear in a dropdown. Select the team that you need access to in the dropdown.

Optionally, enter a reason for the request under **Reason access is needed**, and/or specify a requested duration of access under **Requested access duration**. Finally, click the **Request** button.

Once you submit the request, you will get a Slack message from the P0 bot confirming your request creation. The P0 bot will also send a message to the approvers in the Slack channel designated by your org admin.

1. If your request is approved, you will receive a message from the P0 bot saying that your access has been granted and letting you know when it will expire. You will be automatically added to the GitHub team you requested.
2. **If you are on-call (on a PagerDuty schedule), and your org admin has enabled PagerDuty routing, your access may be automatically approved for 1 hour.**
3. After your request is approved, you'll see a "relinquish" button on the Slack message from the p0 bot. You can optionally use this button to let go of your access early if you finish what you want to do before the expiration time. This will revoke the access, and you must make another request if you need it again.
4. If you wait for the access to expire, you will get a message that it has expired once it does.
5. If your request is denied, you'll receive a message.

GitHub teams can be granted various roles for the organization that contains them as well as the various repositories owned by the organization. This makes them roughly analogous to groups in other IAM systems. You are encouraged to create least-privilege teams for use with P0. For more information, please see GitHub's documentation, [Roles in an organization](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization).

Note that the GitHub integration does not presently support [team membership roles](https://docs.github.com/en/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member). All users are added to teams with the "member" role, which does not grant any ability to modify the team itself.


---

# 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://docs.p0.dev/integrations/resource-integrations/github/requesting-access.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.