> 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/ai-app-builder/refine-an-app/select-a-page.md).

# Select a page

Use the page selector above Preview to open the part of the app you want to inspect or change.

## Open a page

1. Open **Preview**.
2. Find the app address and current route above the preview.
3. Open the dropdown beside the route.
4. Select the page you want to inspect.
5. Confirm the route and the displayed page match your selection.

You can also use the app's own navigation to check the route a user would follow.

## Check the result

For a Tickets page, check its heading and records. Then open a second page and return to Tickets to confirm navigation works.

Selecting a page changes what you are looking at. When requesting an assistant change, also name the page explicitly:

> On the Tickets page, add a Priority filter. Keep the Dashboard page unchanged.

If the list is empty or the page is missing, confirm generation has finished and that the route exists. Inspect [Console and logs](/ai-app-builder/preview-and-troubleshoot/inspect-app-console-and-logs.md) if the page fails to load.

Next: [Edit components in Preview](/ai-app-builder/refine-an-app/edit-components-in-preview.md).


---

# 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/ai-app-builder/refine-an-app/select-a-page.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.