> For the complete documentation index, see [llms.txt](https://docs.talentmap.com/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talentmap.com/knowledge-base/step-5-analyze-interpret-and-report/compass-reports/reporting-faq/can-i-filter-by-questions-in-the-survey.md).
# Can I filter by questions in the survey?
Yes, you are able to filter by any question in your survey, including self-selected demographic items.
1. When running a report, click **Filters.**
2. Click the orange + button to add a new filter.
3. Click the Demographic dropdown and select Survey Item.
> For a ranked choice question, you also select which rank positions to include. Choose the option you want, for example Senior Leadership, then select one or more positions, for example 1st and 3rd. The report then shows only the participants who ranked that option at one of the positions you selected.
>
> Selecting more than one position widens the match. 1st or 3rd returns everyone who ranked the option in either place, not only participants who did both.
> See Ranked Choice Chart for how ranked results are reported.
---
# 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.talentmap.com/knowledge-base/step-5-analyze-interpret-and-report/compass-reports/reporting-faq/can-i-filter-by-questions-in-the-survey.md?ask=&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.
