Set up filters
This feature requires the Enterprise capability tier (the Business ). During the beta, every project is on the free Solo tier, so this feature is locked by default: go to Settings ▸ Billing and request Enterprise access to unlock it.
Filters define the axes along which your content varies: audience, platform, product tier, or any axis relevant to your documentation. You create them on the Filters tab, then apply their values to content as Create conditional content blocks.
Create a filter group
Open Configure and select the Filters tab.
In the name field (placeholder "e.g. Audience, Platform"), type a group name, for example, "Audience," "Platform," or "Product."
Click Add group.
Add values to a filter group
On the Filters tab, find the group's card.
In the Add a value field at the bottom of the card, type a value (for example, for "Audience": "Admin," "Developer," or "End User") and press Enter. Repeat for each value.
Each value gets an automatically assigned color (shown as a dot beside the label) that also appears in the editor.
Choose group names that describe the axis of variation, not specific values. "Audience" is better than "Admin versus User" because it accommodates future values like "Developer" without renaming the group.
Plan your filter groups
Before creating filters, decide which axes of variation your documentation needs:
Filter group | Example values | Use when |
|---|---|---|
Audience | Admin, Developer, End User | Different roles see different features |
Platform | Windows, macOS, Linux | OS-specific instructions |
Product | Free, Pro, Enterprise | Tier-specific capabilities |
Version | v2, v3 | Version-specific content |
Keep filter groups to a minimum. Each additional group multiplies the number of output variants you manage.
Adding a new filter group multiplies your output matrix. Two groups with 3 values each means up to 9 possible combinations. Before adding a third group, verify you actually need separate Publication target settings for those combinations.
A Publication target settings selects one or more values for each group. For example, a target might use this profile:
{
"Audience": ["Admin"],
"Platform": ["Web", "Mobile"]
}This target includes content conditioned for Admin audience and content conditioned for Web or Mobile platforms.
NOT complement
When building condition expressions, the NOT operator excludes content tagged with a specific value. Topicary loads all available filter-group values to correctly compute the complement set, ensuring that NOT "Admin" correctly includes every other value in the Audience group, even values added after the expression was created.
Edit or delete filters
Delete a value with the Remove link beside it. If content uses that value in conditional blocks, the Content health and governance system flags it as a stale condition.
Delete a filter group with the trash icon on the group's card. A confirmation dialog appears, then the group and all its values are removed.
Deleting a filter group removes it from all existing conditional blocks across your project. Content that used those values may no longer filter correctly. Always check which topics use a group before deleting it.
See also
Create conditional content blocks: apply filter values to content after setting up groups
Preview conditioned content: verify conditional blocks in the editor
Conditions versus variables: understand when to use conditions versus variables
Publication target settings: configure condition profiles for publication targets
Content health and governance: how the system flags stale conditions