MANAGE SCHEMAS
Indexed fields and filters
Choose which metadata can be filtered in reports.
Index deliberately
Mark a schema field as indexed when reports need to filter it. Indexing is selective: it supports report filtering without turning every document property into a query field.
Use typed filters
Reports use controls that match the field: enum and boolean selections, numeric minimum/maximum values, date ranges, and Confluence entity pickers. Multiple viewer filters apply immediately.
Change indexed fields safely
A schema update can require reconciliation of existing metadata. Review the impact preview and follow the process in the Processes tab after saving.
What an index enables
Indexing stores selected schema values in a reportable sidecar index. It is the prerequisite for configured report filters and for filtering metadata in the administrative workflow; it does not change the value stored in the metadata document.
Choose fields with stable, useful values: status, owner, review date, risk level or control family are stronger candidates than long free-text evidence notes.
Match the filter to the field
Reports use the field shape to present useful controls: selections for enums and booleans, ranges for numbers and dates, and Confluence entity values for people, pages and spaces. If a newly indexed field has no results, save or reconcile affected metadata so the index is populated.