---
title: Authorization policy version history
description: Version History provides a linear history of changes made to policies and Trust Framework definitions and enables you to publish versions to decision endpoints and Authorize gateways.
component: pingone
page_id: pingone:authorization_using_pingone_authorize:p1az_version_history
canonical_url: https://docs.pingidentity.com/pingone/authorization_using_pingone_authorize/p1az_version_history.html
---

# Authorization policy version history

**Version History** provides a linear history of changes made to policies and **Trust Framework** definitions and enables you to publish versions to decision endpoints and Authorize gateways.

Versions are sorted to display the most recent changes first.

![Screen capture of Version History showing the type of change, entity type, entity name, timestamp, and the user's email address for each version.](_images/btp1678721845715.png)

The following information is shown for each version:

| Column    | Description                                                                                                                                                                             |
| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Action    | The type of change made.                                                                                                                                                                |
| Object    | The type of object that changed. This can be a policy, policy set, rule, statement, or definition. **Definition** includes changes to attributes, services, conditions, and processors. |
| Name      | The name of the object that changed.                                                                                                                                                    |
| Timestamp | The date and time the change was made.                                                                                                                                                  |
| User      | The email address of the user who made the change.                                                                                                                                      |

To help you track changes, you can [name any version](p1az_naming_versions.html). When you reach policy development milestones, you can [publish](p1az_publishing_versions.html) notable points in the version history to [decision endpoints](p1az_decision_endpoints.html) or [Authorize gateways](../integrations/p1_authz_gateways.html). When a named version is no longer published to any endpoints, you can [remove the name](p1az_naming_versions.html) from the version.

|   |                                                                                                                              |
| - | ---------------------------------------------------------------------------------------------------------------------------- |
|   | Each environment can have up to 100 named versions and 500 unnamed versions. The maximum data size for each version is 7 MB. |

Changes to decision endpoints that have corresponding API services are listed under version names that begin with **API Access Management**.

![Screen capture showing the API Access Management Policies version for the Meme Game.](_images/xyq1690825477524.png)

|   |                                                                                                                                 |
| - | ------------------------------------------------------------------------------------------------------------------------------- |
|   | Do not rename these versions. Instead of publishing these versions, [deploy](p1az_deploying_api_services.html) the API service. |