4 More Ways You can Use Queries in Capacities

Queries in Capacities let users build rule-based “views” of objects and then reuse those views anywhere—on tag pages, in weekly reviews, on person pages, or inside custom dashboards. The core payoff is speed and context: instead of manually searching across links, quotes, meetings, milestones, or projects, a saved query keeps the right items grouped and ready wherever the user needs to work.

The first practical use is tag queries. Tags can be applied flexibly—to web links, quotes, and even blocks—so a tag page becomes an entry point into a theme. Rather than only viewing items that share one tag, related tags can be combined into a single query-based view. For example, pulling together items tagged with “curiosity” and “learning” creates a reusable list that can be embedded into other objects. That embedded query can then be reviewed in context, including while writing in a side panel by opening the query object and continuing work without losing the filtered set.

Next comes query-driven reviews, using the weekly review template as a model. A “Sunday review” template can contain a query that returns objects of a chosen type created within a specific date range for that week. The transcript walks through adjusting the date window (e.g., selecting a week where the created-at date falls on or after a given start date and on or before the Sunday of that week) and sorting results by the oldest first. The key advantage is that the review setup is pre-wired: once the template is in place, the query is already waiting to populate the review with the relevant objects.

Users can create their own review queries by starting with an object-type query, selecting what they want to review (meetings, people notes, milestones, and more), and then filtering by created-at dates. The query can be embedded into a week object via template settings so it updates automatically. Still, the calendar sidebar remains the “big overview” option when a full weekly sweep is the goal.

A third example targets colleagues through person-page queries. A query can pull meetings where a text property (the people involved field) includes a specific colleague such as Julie, sorted newest first. When the query is specific enough, it can surface a “new” button that creates a new meeting pre-filled with the colleague’s name and the meeting type—though this behavior may not work when tied to a calendar integration.

Finally, multiple queries can be embedded into a single context page. A “2025” demo dashboard acts like a north star by combining queries for open projects filtered by status (e.g., “in progress”) and a milestone timeline sorted by achievement date. The shared principle across all examples is consistent: once a query is built, it behaves like an object and can be placed wherever it supports the user’s workflow—on tags, in reviews, on people pages, or in year-long planning views.