> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/classic-app-builder/design-and-structure/pages/page-values.md).

# Page Values

In this section you will learn how to use page values

Page Values allow you to pass data from one page to another.&#x20;

{% content-ref url="/pages/-MA3hkw60mFEJNYaR\_ut" %}
[Extract & Pass Values](/classic-app-builder/binding-and-values/parameters.md)
{% endcontent-ref %}

In case, when you want to build a Detail page for your user with the user info on this page: first name, last name, address, etc. You need to pass the user ID from one page to another. To do this you need to create a page value for this page and pass this ID to another page in [Action](/classic-app-builder/actions-and-logic/actions.md).&#x20;

### Create Page values

To create page value, follow the steps:

1. Go to the `Parameters` section
2. Click on the **Add Parameter button**
3. Rename the Parameter as ID

{% @arcade/embed flowId="0PYsECUsHzBJWlwRhrU4" url="<https://app.arcade.software/share/0PYsECUsHzBJWlwRhrU4>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jetadmin.io/classic-app-builder/design-and-structure/pages/page-values.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
