How to filter a database view in Confluence
Filter a Confluence database with Filter, a field, condition and value, then save the configuration as a view when teammates need it.
For example, show only Payments initiatives in Review, leaving the underlying database unchanged. Temporary filters are personal and disappear when you leave or refresh unless saved.
Step-by-step guide
Check the underlying field values
Start from the full table and inspect the values you intend to filter. For a review queue, Stage should use consistent tags rather than free-text variants such as “Review,” “reviewing” and “ready for review.”
Add the exact criteria
Select Filter, choose Product area, set the appropriate condition and select Payments. Add a second filter for Stage is Review. Choose all/AND so each matching initiative satisfies both conditions, rather than any/OR which would broaden the result.
Save a named view
Use the view controls to save the changes to the intended view or create a new one named “Payments review.” Configure layout and visible fields for that reader task. Do not overwrite a shared all-initiatives view merely to make a personal inspection.
Validate positive and negative examples
Confirm a Payments initiative in Review appears, a Payments initiative in Build does not, and an unrelated product’s Review item does not. Refresh the page and reopen the saved view to confirm the configuration persists.
Common mistakes
Mistaking a filter for an access boundary
A filtered view changes what is displayed. It is not an independent security model for the underlying database.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.