---
title: Getting started
description: This guide introduces the dynamic authorization features of the PingAuthorize Policy Editor. It shows you how to create attribute-based access control policies that reflect your business requirements. It also provides a tour of the various concepts involved in modeling policies in the Policy Editor.
component: pingauthorize
version: 11.0
page_id: pingauthorize:pingauthorize_policy_administration_guide:paz_get_started_policy
canonical_url: https://docs.pingidentity.com/pingauthorize/11.0/pingauthorize_policy_administration_guide/paz_get_started_policy.html
revdate: June 17, 2025
section_ids:
  about-this-task: About this task
  steps: Steps
  next-steps: Next steps
---

# Getting started

This guide introduces the dynamic authorization features of the PingAuthorize Policy Editor. It shows you how to create attribute-based access control policies that reflect your business requirements. It also provides a tour of the various concepts involved in modeling policies in the Policy Editor.

## About this task

To get started with the Policy Editor, complete the following tasks:

## Steps

1. Sign on to the Policy Editor.

   In demo environments, you can use the default credential *(tooltip: \<div class="paragraph">
   \<p>Information used to identify a subject for access purposes (for example, username and password). A credential can also be a certificate.\</p>
   \</div>)*:

   * Username: `admin`

   * Password: `password123`

2. Create a branch.

   This branch stores your policies and other entities.

3. Define the Trust Framework.

   This allows you to define the elements that will form the building blocks of your policies—the who, what, when, where, and why.

4. Define your policies and policy sets.

   Build your policies to reflect your business needs.

5. [Test policies and policy sets](paz_visualize_pol_resp.html).

   Verify that your policies correctly implement your business rules.

6. [Commit changes](paz_commit_changes.html).

   This creates a commit, which is an immutable representation of the Trust Framework and Policies at a point in time.

7. [Create a deployment package](../pingauthorize_server_administration_guide/paz_export_deployment_package.html).

   This creates a file that you can deploy to PingAuthorize Server instances across multiple environments.

## Next steps

After you sign on to the Policy Editor, the system prompts you to set the branch on which to work. You can create a new (empty) branch, select an existing branch, or [import a branch](paz_create_branch.html#importing_snapshot_as_branch) from a snapshot file.

The PingAuthorize Policy Editor embraces similar principles to general software source control. When you first deploy the Policy Editor, the `Branches` repository is empty, and the system prompts you to create or import a branch. You must complete one of these actions to continue using the product.

![Screen capture of the Policy Editor's Create a Branch Or Import a Branch from a Snapshot window. Fields include Branch name, Snapshot, and Name.](_images/qpw1577124146026.png)