---
title: Adding an attribute
description: Learn how to use the Trust Framework to add an attribute that you can use in a dynamic authorization policy.
component: pingone
page_id: pingone:authorization_using_pingone_authorize:p1az_tutorial_adding_an_attribute
canonical_url: https://docs.pingidentity.com/pingone/authorization_using_pingone_authorize/p1az_tutorial_adding_an_attribute.html
revdate: April 29, 2026
section_ids:
  steps: Steps
  result: Result:
  next-steps: Next steps
---

# Adding an attribute

Learn how to use the **Trust Framework** to add an attribute that you can use in a dynamic authorization policy.

You need to know the payment amount to determine if it's greater or less than $10,000 USD, so let's add an attribute for the amount to the [Trust Framework](p1az_trust_framework.html).

The **Trust Framework** provides an enterprise-wide view of your data and service ecosystem. It's where your organization's technical personnel capture definitions for digital assets, services, and users across all domains in your organization, including:

* Attributes used in policies

* Connections to APIs

* Information points used as data sources for attributes

When you use business-friendly names to define resources in the **Trust Framework**, policy authors can easily refer to these resources without worrying about how the information is retrieved and populated.

## Steps

1. In the PingOne admin console, go to **Authorization > Trust Framework**.

2. If it isn't already displayed, click the **Attributes** tab.

   You can see the [built-in user attributes](p1_az_built_in_attributes.html) that come with PingOne Authorize. You're going to add a new attribute for the amount.

   ![Screen capture of the Attributes tab in the PingOne Authorize Trust Framework showing the ID attribute nested under PingOne and User.](_images/p1az-tutorial-built-in-attrs.png)

3. Click the **[icon: plus, set=fa]**icon.

4. For the attribute **Name**, enter `Amount`.

   |   |                                                                                                                                                                                                                                             |
   | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   |   | If you selected another attribute before you added `Amount`, `Amount` is nested under the parent attribute. Nesting helps group related attributes together. To keep things simple, you won't nest the `Amount` attribute in this tutorial. |

5. Verify that there is no **Parent** selected. If a parent exists, click the **Delete** icon to remove it.

   To get the payment amount, which is the value of the attribute, you'll add a resolver. [Resolvers](p1_az_resolvers.html) define where the initial data for an attribute comes from.

6. Click **[icon: plus, set=fa]Add Resolver**.

   Keep the default Resolver type of **Request Parameter** so that the value of your attribute comes from a parameter in the decision request. Later in the tutorial, you'll use a field in the decision request body to provide a value for the request parameter. So far your attribute looks like this.

   ![Screen capture of the Details tab for the Amount attribute showing a Request Parameter resolver.](_images/cna1637363639867.png)

   Next let's make sure that the value of the attribute is a number.

7. In **Value Settings**, for the **Type**, select **Number**.

   ![Screen capture of Value Settings for the Amount attribute showing that the Type is Number.](_images/eqm1637364049051.png)

8. Click **Save Changes**.

   ### Result:

   Your new attribute is displayed in the attribute list.

   ![Screen capture of the Amount attribute on the Attributes tab.](_images/p1-az-tutorial-attr-result-list.png)

## Next steps

You used the **Trust Framework** to create a simple attribute that represents the payment amount. Now that you've added an attribute, you're ready to [use the attribute in a policy](p1az_tutorial_adding_and_testing_policies.html#tutorial-add-policy).