---
title: Publishing an authorization policy version
description: You can publish notable points in Version History to deploy policies and Trust Framework definitions to decision endpoints or to Authorize gateways.
component: pingone
page_id: pingone:authorization_using_pingone_authorize:p1az_publishing_versions
canonical_url: https://docs.pingidentity.com/pingone/authorization_using_pingone_authorize/p1az_publishing_versions.html
section_ids:
  steps: Steps
  result: Result:
---

# Publishing an authorization policy version

You can publish notable points in **Version History** to deploy policies and **Trust Framework** definitions to decision endpoints or to Authorize gateways.

Publishing a version is like saving a snapshot of your policies and **Trust Framework** definitions. The published version reflects the state of these objects at a specific point in time. Learn more in [Version history](p1az_version_history.html).

By default, PingOne Authorize provides three decision endpoints for every environment: **Dev**, **Test**, and **Prod**. You can publish a version to multiple decision endpoints or Authorize gateways, but each decision endpoint can have only one version published to it at a time. The version is replaced each time you publish to an endpoint or an Authorize gateway. If an endpoint is set to [use the latest version](p1az_decision_endpoints.html), updated versions are published to it automatically.

Use the following steps to publish versions to decision endpoints. To publish versions to Authorize gateways, go to [Publishing authorization policy versions to Authorize gateways](../integrations/p1_publish_policy_versions_to_authz_gateway_instances.html).

|   |                                                                                                                                                                  |
| - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | Ensure that your policies and **Trust Framework** definitions are thoroughly tested before you publish them to the **Prod** endpoint and use them in production. |

## Steps

1. In the PingOne admin console, go to **Authorization > Version History**.

2. Click the **More Options (⋮)** icon next to the version that you want to publish and select **Publish Version**.

   ![Screen capture showing the Publish Version option in the More Options menu.](_images/pmi1637451512784.png)

   |   |                                                                                                                                                                             |
   | - | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   |   | Do not publish versions with names that begin with **API Access Management**. Instead, [deploy](p1az_deploying_api_services.html) the API service to publish these changes. |

3. In the **Publish to** list, select an endpoint.

4. For version **Name**, enter a name that makes the version easy to identify.

   If there's already a name, you can keep it or update it. The name is used as a tag in [audit events](p1az_monitoring_decision_endpoint_events.html).

5. Click **Publish**.

   ### Result:

   The version name and the endpoints that the version is published to are displayed in **Version History**.