> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/form-designer/pages/page-navigator.md).

# Pages Navigator

## 📖 What is the pages navigator

The page navigator allows you to let the respondent navigate through your survey pages using tabs or side bars that are displayed on either on the top of the survey or on the left or right of it. 

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MBrELaKyaykiPk3kdzs%2F-MBrEvvJ-d8dYc_PcUGD%2Fimage.png?alt=media\&token=94ea2cce-c443-45d6-bc39-73fd54383d8f)

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MOB84AarjsTYQLr84SW%2F-MOB8FXVhHVt8Q_DJ5Jl%2Fimage.png?alt=media\&token=b9335d33-3b3f-4e1f-8f85-e4a393108066)

Using these tabs or using the side navigation respondents can go to any pages in no particular order.

## 🔅 Pages navigator properties

You may set the page navigator properties from the [footer manager](/form-management/form-designer/footer-manager.md) page.

* **`Validate page on page change`** checks that all questions have been answered correctly before letting the respondent switch to another page.
* **`Ignore invalid page on submit`** you can still allow the submit of respondent's answers even if the respondent did not visit pages that had required questions on them.
* **`Disable unvisited pages`** will restrict access to the pages that were already displayed to the respondent.


---

# 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.ngsurvey.com/form-management/form-designer/pages/page-navigator.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.