Content filters
Content filters let you restrict which indexed content a domain answers from, using DITAVAL-style include/exclude rules. They are available on all domain types at Settings → Content filters , and the rules apply uniformly across every channel — widget, Slack, MCP, and API.
Each rule row has three parts:
- Attribute — the metadata attribute to match (e.g.
audience). - Value — the attribute value to match (e.g.
admin). - Rule — a dropdown set to Include or Exclude.
- Include — only surface content tagged with this attribute=value pair.
- Exclude — hide content tagged with this attribute=value pair.
An empty rule set means all indexed content is available. If the same attribute=value pair appears in both an Include and an Exclude row, saving is blocked until the conflict is resolved.
Tip
Content filters work together with access-control metadata tokens. A user
whose signed token does not carry matching attributes will not see restricted content. See
Access control for how to enforce
per-user filtering.
FAQ
What are content filters and where do I configure them?
Content filters let you restrict which indexed content a domain answers from using DITAVAL-style include/exclude rules. They’re available for all domain types under Settings → Content filters. The same rules apply uniformly across every channel, including the widget, Slack, MCP, and the API.
How do I define content filter rules (attribute, value, include/exclude)?
Each rule row has three parts: an Attribute (the metadata attribute to match, such as audience), a Value (the attribute value to match, such as admin), and a Rule set to Include or Exclude. Include means only content tagged with that attribute=value pair is surfaced, while Exclude hides content tagged with that pair.
What happens if I leave the content filter rule set empty or create conflicting rules?
If you leave the rule set empty, all indexed content is available. If the same attribute=value pair appears in both an Include and an Exclude row, saving is blocked until you resolve the conflict.
How do content filters interact with access-control metadata tokens?
Content filters work together with access-control metadata tokens. If a user’s signed token does not carry matching attributes, they will not see restricted content. For enforcing per-user filtering, refer to the Access control documentation.