> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/salesforce/setting-up/filtering-rules/hidden-filters.md).
# Hidden Filters
**LFS Version requirement:** v12.20 or later
This feature introduces an extension to the existing [rules for filtering the offer catalog](https://docs.limio.com/salesforce/setting-up/filtering-rules).
**Introduction:**
#### Considerations for User Interface Design
Our Limio for Salesforce Offers Catalog focuses on a clear and easy-to-use interface. While mandatory filters like "Country" and "Sales Channel" are crucial, they can clutter the interface. To improve the user experience, we are introducing a feature to hide certain filters from the interface, using their values to select the right offers.
**How it works:**
* Navigate to the **Offers Filtering Rules**
* Open an existing rule or create a new one. Select filters to be preloaded in the catalog.
* Each filter card has a new toggle called "Is Hidden", inactive by default.
* **Enable "Is Hidden" Checkbox:**
* Activate "Is Hidden" toggle on the filters you'd like to hide from the UI.
* Save configuration.
While not visible to users, the values of selected filters are still used in queries to retrieve offer results.
**Note:** Hidden filter options are **excluded** from the "Add more filters" dropdown to avoid inadvertent changes.
### Tips
1. In the Catalog, the **Country** and **Sales Channel** filters are always preloaded, even if not explicitly selected in the rule. To hide them, include these filters in the rule, activate the *Is Hidden* property, and save the configuration.
2. Adjustments to the Catalog Filters panel will directly affect the query used to fetch offers from Limio.
---
# 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.limio.com/salesforce/setting-up/filtering-rules/hidden-filters.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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)