🚀Request Access Quickstart
Request your first just-in-time access to a cloud resource through Slack, Microsoft Teams, the P0 web app, or the CLI. A quickstart for developers and engineers.
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.
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 guide instead.
Before you start
Confirm the following:
Your organization has a P0 account and at least one resource integration installed
You can sign in to 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 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:
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 installed
Step 2: Request access
Open Slack and navigate to any channel.
Type
/p0 requestand press Enter. The P0 request modal opens.Select the resource type (such as AWS, Google Cloud, or Kubernetes).
Select the specific resource and access level you need.
Enter a reason for your request. This helps approvers understand the context.
Select a duration for how long you need access.
Click Request.
P0 sends you a direct message with your request details and routes the request to the appropriate approver.
If you know exactly what you need, skip the modal with a slash command:
See requesting access via Slack for the full command syntax.
Open Microsoft Teams and navigate to any channel or chat.
Type
@P0 Security requestand send the message. The P0 request card opens.Select the resource type (such as AWS, Google Cloud, or Kubernetes).
Select the specific resource and access level you need.
Enter a reason for your request. This helps approvers understand the context.
Select a duration for how long you need access.
Click Request.
P0 sends you a message with your request details and routes the request to the appropriate approver.
Your P0 administrator must install the Microsoft Teams integration before you can use this method.
Sign in to p0.app.
Navigate to Access Management in the left sidebar.
Click the Request Access button in the top right corner.
Select the resource type, resource, and access level you need.
Enter a reason and select a duration.
Click Submit.
Your request appears in the Pending section of the Access Management Activity page.
See web request modal for more details.
Install the P0 CLI if you haven't already. See installing the P0 CLI.
Authenticate:
Request access. For example, to request an AWS IAM role:
To request access and wait until it's provisioned before running a command, add the
--waitflag:
See p0 request for the full command reference and all supported providers.
Step 3: Get approved and use your access
After you submit your request:
Wait for approval. P0 routes your request to the appropriate approver based on your organization's access policies. You receive a notification when access is approved or denied.
Use your access. Once approved, P0 provisions access automatically. Depending on the resource, expect a short propagation delay (10 seconds to one minute).
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.
Most IAM systems have a propagation delay of 10 to 30 seconds after access is provisioned before you can use it.
Troubleshooting
/p0 request does not respond in Slack
Confirm that the P0 Slack bot is installed. Ask your P0 administrator to check the Slack integration.
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.
"This resource doesn't exist" error
Your organization's access policy may not cover this resource. Contact your P0 administrator. See access policies.
CLI returns an authentication error
Run p0 login to re-authenticate. See p0 login troubleshooting.
Access approved but not working
Wait 30 seconds for IAM propagation. If access still does not work, check the requesting access guide for resource-specific details.
What's next
Last updated