Skip to main content
Filters let your team set rules that ClarityQ applies automatically when it queries your data — for example, “always exclude test accounts” or “restrict this table to the past 24 months”. They keep answers consistent across every chat and dashboard, without requiring each user to remember the rules. ClarityQ supports two kinds of filters.

​
Mandatory Filters

Mandatory filters are SQL WHERE conditions attached to a table in the Table Catalog. Every query that hits the table — whether the agent wrote it, an automation triggered it, or a dashboard refreshed it — has the filter appended automatically. Users don’t see the filter applied; they just get the scoped result. Common uses:
  • Excluding internal accounts, test users, or staff emails.
  • Restricting time ranges (for example, only the last 24 months of events).
  • Enforcing tenancy on multi-tenant tables so each product team sees only its own slice.
Mandatory filters are configured with ClarityQ during onboarding and updated when your data model evolves.

​
Changing Mandatory Filters

Changing a table’s mandatory filters is not applied retroactively — anything already built on that table keeps the filtering it had when it was created. What that means depends on the table:
  • The Events table — Changing its mandatory filters only affects future feature creation. Existing features are not updated automatically and must be reviewed manually.
  • Any other table — The change is not applied automatically to existing entities, dimensions, metrics, or segments that use the table.
Because a filter change doesn’t propagate to existing components, review the impact before you make it. After changing the filters, use the Context Builder to find everything that references the table and update it as needed, so answers stay consistent and accurate.

​
Question Filters

Question filters live at the product level and scope what the agent considers when it answers an Ask Anything question. Unlike mandatory filters, they’re visible in the chat UI when relevant — for example, picking a country or app version before the agent runs the query. Question filters are set up alongside the rest of your product configuration. Reach out to your ClarityQ contact when you want to add or change one.

​
When to Use Which

Mandatory filters apply globally and silently — use them to enforce rules everyone must follow. Question filters give analysts choices that change the scope of an answer — use them when there are several valid ways to slice the data and you want the user to pick.