Custom Filters
The semantic layer (“Knowledge Base”) is designed to make complex data intuitive and accessible. But in their raw form, even the richest data models can overwhelm users with unnecessary noise. Filters address this challenge by applying rules or conditions that restrict the data returned from queries. They enforce boundaries such as time ranges, permissions, and quality checks — ensuring that only the most relevant and approved data flows into LumiAI’s agentic workflows for analysis.
When are Filters Useful?
Filters serve different purposes depending on the stakeholder:
Governance & Access Control: Filters enforce permissions aligned with roles and responsibilities. For example, a conglomerate with multiple subsidiaries could create separate Knowledge Bases based on Member Company ID, ensuring that users from one subsidiary cannot access privileged information from another.
Relevance to Business Stakeholders (Segmentation): Business users don’t need every field from a dataset — just the subset that matters to their use case. Filters declutter the experience and surface only the data that drives decisions.
Standardization & Transparency: By applying filters at the semantic layer, all stakeholders work from the same source of truth. This prevents inconsistencies in reporting, improves reusability, and enhances traceability of results.
Guardrail Autonomy for AI Agent: Filters act as invisible oversight for LumiAI’s agents. They ensure that recursive, autonomous workflows stay relevant, efficient, and compliant, which increases trust in the outputs.
How to Apply Custom Filters:
Add a Custom Filter
Filters are applied at the Table level within your Knowledge Base. They can be found directly under the field sub-section of the table you select.


Configure the Custom Filter
Because you’ve already defined fields in your Knowledge Model, you can apply filters to each of them.
You can create filters in three simple steps:
Select the field you want to filter on.
Choose the appropriate comparator (e.g., equals, greater than, contains).
Enter the final criteria.
Below is an example of how we applied a filter criterion to capture only sales orders that occurred after August 1, 2025.

Validate Custom Filter Application
The table preview feature provides visibility into your data, helping you apply the right business rules with confidence.

Last updated
Was this helpful?