Access Policy Scope
< details | access policy create workflow

Overview
- Workspaces: Select which developer workspace(s) the policy will apply to. Scoping a cluster access policy to a workspace allows you to provide additional roles to a specific workspace that has, for example, different requirements to your default platform-wide roles.
- Stages: Choose the stage(s) where the policy will be enforced to ensure consistent access privileges across clusters. This enables you to apply different policies for production and non-production environments.
📚 For more details on key points, refer to the overview section.
📚 Explore the properties section for additional information on each UI property.
CLI Instructions
Follow the instructions in the details section.
Web Interface Instructions
Steps
- Fill in the scope details as outlined in the properties section.
- Click Continue to proceed
Screenshot(s)

Properties
Field | Description |
---|---|
Workspace | The workspace(s) where the access policy is applied. A workspace is where teams provision and manage applications, environments, clusters, and cloud resources. Scoping an access policy to a workspace allows you to provide additional roles to a specific workspace that has, for example, different requirements to your default platform-wide roles. |
Stage | The stage(s) where this cluster access policy is applied. A [stage]/wayfinder/admin/stages/stages-overview is used to isolate and test resources at the infrastructure level. Adding a stage to a access policy restricts its availability to that specific stage, such as production or non-production. |