> 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/getting-started/request-access-quickstart.md).

# Request Access Quickstart

This quickstart walks you through requesting your first just-in-time access to a cloud resource. By the end, you will have submitted an access request using Slack, Microsoft Teams, the P0 web app, or the P0 CLI.

{% hint style="info" %}
This guide is for developers and engineers who need to request access to resources. If you are an administrator setting up P0, start with the [Getting started with just-in-time access](/getting-started/getting-started-with-just-in-time-access.md) guide instead.
{% endhint %}

## Before you start

Confirm the following:

* Your organization has a P0 account and at least one [resource integration](/integrations/resource-integrations.md) installed
* You can sign in to [p0.app](https://p0.app) with your organizational email
* *(For Slack requests)* The P0 Slack bot is installed in your workspace
* *(For Microsoft Teams requests)* The [P0 Microsoft Teams integration](/integrations/notifier-integrations/microsoft-teams.md) is installed in your organization

## Step 1: Choose your request method

P0 supports four ways to request access. Select the one that fits your workflow:

| Method              | Best for                                                      | What you need                                                                                      |
| ------------------- | ------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| **Slack**           | Quick requests without leaving your chat workflow             | P0 Slack bot in your workspace                                                                     |
| **Microsoft Teams** | Quick requests without leaving your chat workflow             | [P0 Microsoft Teams integration](/integrations/notifier-integrations/microsoft-teams.md) installed |
| **Web app**         | Browsing available resources before requesting                | Access to [p0.app](https://p0.app)                                                                 |
| **CLI**             | Scripted workflows or requesting and using access in one step | [P0 CLI installed](/p0-cli/installing-p0-cli.md)                                                   |

## Step 2: Request access

{% tabs %}
{% tab title="Slack" %}

1. Open Slack and navigate to any channel.
2. Type `/p0 request` and press Enter. The P0 request modal opens.
3. Select the **resource type** (such as AWS, Google Cloud, or Kubernetes).
4. Select the specific **resource** and **access level** you need.
5. Enter a **reason** for your request. This helps approvers understand the context.
6. Select a **duration** for how long you need access.
7. Click **Request**.

P0 sends you a direct message with your request details and routes the request to the appropriate approver.

{% hint style="info" %}
If you know exactly what you need, skip the modal with a slash command:

```
/p0 request gcloud role my-project viewer --reason "Investigating production issue"
```

See [requesting access via Slack](/access-management/just-in-time-access/requesting-access.md#using-slack-slash-commands) for the full command syntax.
{% endhint %}
{% endtab %}

{% tab title="Microsoft Teams" %}

1. Open Microsoft Teams and navigate to any channel or chat.
2. Type `@P0 Security request` and send the message. The P0 request card opens.
3. Select the **resource type** (such as AWS, Google Cloud, or Kubernetes).
4. Select the specific **resource** and **access level** you need.
5. Enter a **reason** for your request. This helps approvers understand the context.
6. Select a **duration** for how long you need access.
7. Click **Request**.

P0 sends you a message with your request details and routes the request to the appropriate approver.

{% hint style="info" %}
Your P0 administrator must install the [Microsoft Teams integration](/integrations/notifier-integrations/microsoft-teams.md) before you can use this method.
{% endhint %}
{% endtab %}

{% tab title="Web app" %}

1. Sign in to [p0.app](https://p0.app).
2. Navigate to **Access Management** in the left sidebar.
3. Click the **Request Access** button in the top right corner.
4. Select the **resource type**, **resource**, and **access level** you need.
5. Enter a **reason** and select a **duration**.
6. Click **Submit**.

Your request appears in the **Pending** section of the Access Management Activity page.

See [web request modal](/access-management/just-in-time-access/requesting-access/web-request-modal.md) for more details.
{% endtab %}

{% tab title="CLI" %}

1. Install the P0 CLI if you haven't already. See [installing the P0 CLI](/p0-cli/installing-p0-cli.md).
2. Authenticate:

   ```bash
   p0 login
   ```
3. Request access. For example, to request an AWS IAM role:

   ```bash
   p0 request aws role MyReadOnlyRole \
     --account 123456789012 \
     --reason "Investigating S3 access issues"
   ```
4. To request access and wait until it's provisioned before running a command, add the `--wait` flag:

   ```bash
   p0 request aws role MyReadOnlyRole \
     --account 123456789012 \
     --reason "Investigating S3 access issues" \
     --wait
   ```

See [`p0 request`](/p0-cli/p0-commands-and-usage/p0-request.md) for the full command reference and all supported providers.
{% endtab %}
{% endtabs %}

## Step 3: Get approved and use your access

After you submit your request:

1. **Wait for approval.** P0 routes your request to the appropriate approver based on your organization's [access policies](/access-management/just-in-time-access/request-routing.md). You receive a notification when access is approved or denied.
2. **Use your access.** Once approved, P0 provisions access automatically. Depending on the resource, expect a short propagation delay (10 seconds to one minute).
3. **Access expires automatically.** When the approved duration ends, P0 revokes access. You can also click **Relinquish** in your P0 Slack or Microsoft Teams message to give up access early.

{% hint style="warning" %}
Most IAM systems have a propagation delay of 10 to 30 seconds after access is provisioned before you can use it.
{% endhint %}

## Troubleshooting

| Problem                                             | Solution                                                                                                                                                                                                                      |
| --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `/p0 request` does not respond in Slack             | Confirm that the P0 Slack bot is installed. Ask your P0 administrator to check the [Slack integration](/integrations/notifier-integrations/slack.md).                                                                         |
| P0 Security bot does not respond in Microsoft Teams | Confirm that the P0 Microsoft Teams integration is installed and the app is available to users. Ask your P0 administrator to check the [Microsoft Teams integration](/integrations/notifier-integrations/microsoft-teams.md). |
| "This resource doesn't exist" error                 | Your organization's access policy may not cover this resource. Contact your P0 administrator. See [access policies](/access-management/just-in-time-access/request-routing.md).                                               |
| CLI returns an authentication error                 | Run `p0 login` to re-authenticate. See [p0 login troubleshooting](/p0-cli/troubleshooting/p0-login.md).                                                                                                                       |
| Access approved but not working                     | Wait 30 seconds for IAM propagation. If access still does not work, check the [requesting access](/access-management/just-in-time-access/requesting-access.md) guide for resource-specific details.                           |

## What's next

* [Request access on behalf of another user](/access-management/just-in-time-access/requesting-access/for-another-party.md)
* [Use the P0 CLI for AWS role assumption](/p0-cli/p0-commands-and-usage/p0-aws-role-assume.md)
* [Use the P0 CLI for SSH access](/p0-cli/p0-commands-and-usage/p0-ssh.md)
* [Browse the full requesting access guide](/access-management/just-in-time-access/requesting-access.md)


---

# 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:

```
GET https://docs.p0.dev/getting-started/request-access-quickstart.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.