---
title: Enabling query settings
description: To include an attribute without explicitly providing its value in a query decision request, you must enable query settings for that attribute.
component: pingauthorize
version: 11.0
page_id: pingauthorize:pingauthorize_policy_administration_guide:paz_enabling_query_settings
canonical_url: https://docs.pingidentity.com/pingauthorize/11.0/pingauthorize_policy_administration_guide/paz_enabling_query_settings.html
revdate: December 10, 2025
section_ids:
  steps: Steps
  example: Example:
  result: Result
---

# Enabling query settings

To include an attribute without explicitly providing its value in a [query decision request](../pingauthorize_server_administration_guide/paz_json_pdp_api_flow.html#json_pdp_query_requests), you must enable query settings for that attribute.

|   |                                                                                                                                                |
| - | ---------------------------------------------------------------------------------------------------------------------------------------------- |
|   | To include attributes with query settings enabled in decision requests, you must include such attributes in at least one authorization policy. |

To enable query settings:

## Steps

1. In the **Trust Framework**, navigate to the attribute for which you want to enable query settings.

2. In the attribute's hamburger menu, select **Add Query Settings**.

   ![Screen capture of an attribute hamburger menu with the Add Query Settings option selected](_images/bcr1701468601295.png)

   |   |                                                                    |
   | - | ------------------------------------------------------------------ |
   |   | Before enabling query settings, you must save the query attribute. |

3. In the **Source** list of the **Query Settings** section that you created, select a source attribute of the **Collection** type.

   This attribute defines the collection of possible query attribute values that the decision engine retrieves to test against the appropriate policy.

   ![Screen capture of the Value Settings section of a query attribute definition with Collection selected as the Type](_images/vji1701468842517.png)

   |   |                                                                                                                               |
   | - | ----------------------------------------------------------------------------------------------------------------------------- |
   |   | Using a source collection attribute with a significant number of values could strain the system and cause performance issues. |

4. (Optional) In the **Response Value** list, select an attribute with which to filter the decision response.

   |   |                                                                      |
   | - | -------------------------------------------------------------------- |
   |   | You cannot use the same value for **Source** and **Response Value**. |

   ### Example:

   ![Screen capture of the Query Settings section of a query attribute with example attributes selected for the Source and Response Value fields](_images/nyu1701468927669.png)

   In this example, **UsersService** is an attribute that resolves from an HTTP service call retrieving a collection of `User` objects. Given a JSON `User` object such as the following, the **User.name** sub-attribute resolves from the **User** attribute and is configured with a JSONPath value processor to extract the `name` field:

   ```json
   {
     "name": "Joe Boggs",
     "id": "b5f963fa-111e-49ff-994b-b89a20a2c1d5",
     "age": 27
   }
   ```

   ![Screen capture of an example value processor on the User.name attribute extracting the $.name field from the JSON user object](_images/gup1701635243723.png)

   With the **User.name** attribute selected as the **Response Value**, requests that query the **User** attribute will only return the name of the relevant user, rather than the entire user object.

   ```
   "results": [
     {
       "attribute": "User",
       "value": "Joe Boggs",
       "decision": "PERMIT"
     }
   ]
   ```

   To return the entire value of the query attribute, leave **Response Value** blank.

5. Click **Save**.

## Result

You can now include this attribute in the `query` array of a query decision request without assigning it any values.