Search and filters are how you find things once a workspace fills up. Search is fast, full-text, and works across the whole workspace. Filters ask more structured questions inside a single category or project.

Both respect access the same way the rest of the app does: you only ever search and filter the records you are allowed to see.

Search looks across the whole workspace at once and matches on more than titles.

• Full text: names, descriptions, document text, and form field values are all searchable.
• Highlighted results: matches come back with a short snippet so you can see why something matched.
• Everything, together: one query can surface categories, pages, projects, tasks, files, forms, and users side by side.

Facets narrow a search to one kind of thing — just pages, just tasks, just files, and so on — when you already know the shape of what you are looking for.

The same search is built into the pickers used throughout the app, so choosing a category, assigning a user, or attaching a form all draw on it. When you have permission to create a kind of record, search can also create it on the spot if it is not there yet.

Filters answer structured questions about the records under one category (its pages) or one project (its tasks). A filter is a set of conditions, each a field, a comparator, and a value, combined so that every condition must match.

• Text: contains, matches, or is one of a list.
• Numbers: equals, less than, greater than, or between.
• Dates: before, on or after, or between.
• Yes/no and lists: checkbox state, and list fields that contain a value or any of several.

You can preview a filter’s results before saving it, and a saved filter becomes a reusable view with its own columns. Because form fields can be filtered, a filter can reach into the structured data on each record, not just its name and dates.

Search and filter results are scoped to the current user. Two people can run the same query and see different results, and restricted content never appears in either place — it is left out as results are gathered, not hidden afterward.

That makes search and filters safe to use freely: there is no query that quietly reaches past someone’s permissions.

The AI assistant uses the same filter engine. It can look up which fields a project or category exposes, then run a read-only structured query over that project’s tasks or that category’s pages on your behalf.

• Search is for finding records quickly, not a reporting or business-intelligence tool.
• Filters live on a specific category or project rather than spanning the whole workspace at once.
• A newly changed record refreshes its search and filter data shortly after it is saved, so a brand-new value can take a moment to appear.
• A filter with many overlapping conditions is easier to reason about when the underlying forms are named and structured with a little intention.