> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/consume/discover/search-the-hub/filters.md).

# Filters

Narrow the Hub by domain, glossary terms, tags, type, and members.

Filters narrow the Hub to the products that match specific metadata. Use them when the list is large and you want to focus on a domain, a glossary term, a set of tags, a product type, or the members behind a product. Filters and keyword [search](https://v2.dataos.info/consume/discover/search-the-hub.md) work together: search matches text, filters match structured metadata.

## Use the filters

The filters sit as dropdowns to the right of the search field. Open a dropdown and select one or more values; the filter applies as soon as you select a value. The **All**, **Favorites**, and **My data products** tabs work alongside filters, so you can filter across the tenant, only your starred products, or only what you own or are a member of.

* **Domain:** focus on one business area. Use it when you know which part of the business owns the data.
* **Terms:** narrow to products linked to a glossary term.
* **Tags:** narrow to a topic, source, or convention your team uses. The dropdown has a search box and includes system tags.
* **Type:** limit to a product type, such as **Source aligned**.
* **Members:** find products owned or maintained by a specific person, so you know who to trust or contact.

A dot marks each active filter, and the Hub shows the result count. Select **Reset all** to clear every filter and return to the full list.

Next: open a promising product and continue to [Evaluate](https://v2.dataos.info/consume/evaluate/overview.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://v2.dataos.info/consume/discover/search-the-hub/filters.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.
