> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/how-to-guides/product-finders/finder-editor.md).

# Finder Editor

The Finder Editor allows you to customize and manage the pages, questions and answers within your flow. This documentation will help you tailor each step of the user's recommendation journey.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Page Settings</strong><br><br>Configure the layout, advanced styling, and behavior of each page in your Finder flow</td><td><a href="/how-to-guides/product-finders/finder-editor/page-settings.md">Page Settings</a></td></tr><tr><td><strong>Question Editor</strong><br><br>Define question content, logic, and structure to guide users effectively</td><td><a href="/how-to-guides/product-finders/finder-editor/question-editor.md">Question Editor</a></td></tr><tr><td><strong>Answer Editor</strong><br><br>Customize answer options, filtering, and ranking to refine product recommendations</td><td><a href="/how-to-guides/product-finders/finder-editor/answer-editor.md">Answer Editor</a></td></tr></tbody></table>


---

# 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.crobox.com/how-to-guides/product-finders/finder-editor.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.