For the complete documentation index, see llms.txt. This page is also available as Markdown.

📋Policy Studio

Define the access policies and Access Bundles that decide who can request which resources, and how those requests get approved.

Policy Studio is where you define the rules that route and approve access requests. Access Management, a separate screen, is where users submit and track those requests.

Benefits of Policy Studio

  • Route requests to the right approver automatically, instead of sending every request to your Security Reviewers.

  • Group several resource accesses into a single requestable Access Bundle, so a user requests everything a task needs in one step.

  • Apply consistent approval rules across AWS, Google Cloud, Azure, Kubernetes, and SSH access, instead of configuring each integration on its own.

How it works in P0

Policy Studio has two views. Control holds your access policies, shown as a table or as YAML. Access Bundles groups several resources into one requestable item, such as everything a new engineer needs on their first day.

When a user requests access in Access Management, P0 checks your Policy Studio configuration to decide who approves the request, or whether to approve it automatically. Bundles are configured only in Policy Studio, and can't be edited as YAML.

Get started with Policy Studio

Follow the Configure your first access policy tutorial for a hands-on walkthrough.

Last updated