Configure report filters and viewer controls — Simpleasyty

Help Center — Configure report filters and viewer controls

GETTING STARTED

Introduction Quick start

CREATE A SCHEMA

Create a schema from a template Create a schema from scratch

SCHEMA TEMPLATES

Security Risk Register ISO 27001 Document Control SOC 2 Evidence Register Policy Management Third-Party Risk Data Classification Application Portfolio Controlled Document Architecture Decision Record Information Asset Register Business Continuity Register GDPR Processing Activity

IMPORT

Import a JSON or YAML schema package Import Page Properties

FIELD TYPES

Schema field types Text fields Number fields Yes / No fields Single choice fields Date / Time fields Email fields URL fields Confluence reference fields List fields Field group fields

MANAGE SCHEMAS

Manage schemas Indexed fields and filters Schema permissions

CAPTURE DATA ON PAGES

Capture metadata on a page Capture, validate and repair metadata

CREATE REPORTS

Build a Metadata Report Configure report filters and viewer controls

STORAGE & PRIVACY

Data residency Storage in Forge Retention and deletion

COMPLIANCE

Compliance workflows Metadata, history and revisions

ADMINISTRATION & TROUBLESHOOTING

Import and export Schema reconciliation and processes Security, storage and limits Troubleshoot schemas, filters and reports

Before you begin

Check these requirements before following the steps below.

A Metadata Report configured with a schema.
Schema fields marked indexed when they need to be filtered.

1
Add fixed filters
Use fixed filters to define the metadata to include in the published report. They constrain the report configuration and remain in effect for every reader.
2
Expose viewer filters
Expose only indexed fields that readers genuinely need. The report uses controls that match the field: selections for enums and booleans, ranges for numbers and dates, and Confluence pickers for people, pages and spaces.
3
Choose viewer actions
Enable search, sorting, grouping, full screen or CSV download only when they help the audience. Viewer changes stay local to the current report view; they do not rewrite page metadata.