The Property Group Report helps you review the same structured information across many Confluence pages in one place. Use it when a property group is already applied on multiple pages and you want a clear overview for tracking, filtering, sorting, and updating values at scale.

Best fit: use the Properties byline to edit values on a single page, the Display Property Groups macro to show metadata inside page content, and the Property Group Report to compare that metadata across many pages.

1 What the report does
2 Before you create a report
3 How to add a Property Group Report
4 How to configure the report
5 Filter the report
6 Work with the report after publishing
7 Edit values directly in the report
8 Recommended setup patterns
9 Common issues and how to think about them
10 Practical guidance

What the report does

The report collects pages or blog posts that use the same property group and displays their values in a structured view. In practice, that means each matching page becomes a row, and each property becomes a column.

See many records at once instead of opening pages one by one
Compare values consistently across teams, projects, or documents
Filter results to focus on the records that matter
Sort by a property to make trends and priorities easier to spot
Edit directly in the report for faster maintenance workflows

Screen Recording 2026-07-03 at 09.29.52.mov

Use this when	Recommended feature

Use this when	Recommended feature
You want to update metadata on one page while reading it	Byline Properties
You want key property values visible inside the page body	Display Property Groups macro
You want a cross-page overview of the same property group	Property Group Report

Before you create a report

A report only becomes useful when there is already data to collect. Before inserting the macro, make sure the selected property group is actually being used on pages.

Create or reuse a property group in the editor
Attach that property group to the pages you want to track
Fill in at least some values from the page-level Properties panel or existing macro-based workflow
Then insert the Property Group Report macro on a summary page

The new Properties experience starts from the page-level inline Properties panel. The report is a separate reporting surface used after property groups are already in use across pages.

How to add a Property Group Report

Open the Confluence page where you want the report to appear.
Edit the page.
Open the macro picker.
Search for Property Group Report.
Select the macro.
In the macro configuration, choose the property group you want to report on.
Adjust the display and filter settings.
Save the macro and publish the page.

Once published, the report displays all matching pages that contain the selected property group, subject to the filters you configured.

How to configure the report

The report configuration determines which records appear and how they are shown. A good setup keeps the report focused and easy to scan.

Setting	What it controls	How to use it

Setting	What it controls	How to use it
Property group	The dataset the report is built from	Select the group used on the pages you want to track
Displayed properties	Which columns appear in the report	Show only the fields readers need for review or comparison
View type	The report layout	Choose table for dense review; use card view where supported for lighter scanning
Sort by	Default order of results	Sort by the property most useful for prioritisation, such as date or status
Add entries	How new records can be created from the report	Choose inline, dialog, or disable it if the report should stay read-only
Limit	How many records are shown	Keep the list focused, especially on busy spaces

Start with a simple table that shows only the most important columns, such as Name, Status, Owner, and Due Date. You can always add more later.

Filter the report

Filters help narrow the results so readers see the right subset of pages. This is especially useful when the same property group is used widely across a space or across multiple teams.

Filter	What it does	Notes

Filter	What it does	Notes
Property Value(s)	Shows records with specified property values	Useful for filtering by structured fields such as select-like values
Label(s)	Limits results to pages with selected Confluence labels	Multiple values in one filter act as OR; multiple label filters act as AND
Space(s)	Limits results to selected spaces	Useful in multi-space rollup reports
Pages under	Limits results to content under selected parent pages	Helpful for project folders, team sections, or documentation trees

Work with the report after publishing

After the page is published, the report becomes a working surface for reviewing and maintaining data.

Scan the rows to review all matching pages in one place
Use column headers to sort the table by a property
Edit values directly in the report where supported
Apply live filters from the report view to narrow results without reconfiguring the macro
Open the source page from the Name column when you need more context

A well-configured report can serve as a lightweight operations table for recurring work such as project tracking, content governance, release checklists, or team directories.

Edit values directly in the report

One of the most useful report features is direct editing. Instead of opening each page individually, users can click into a value in the report and update it there.

Find the row for the page you want to update.
Click the row to edit.
Enter the new value.
Press Enter or click outside the field to save.

This is especially helpful for quick maintenance tasks such as changing status values, owners, dates, or other structured fields across many records.

Use direct editing for quick updates. If you need to change the structure of the property group itself, such as adding fields or changing field types, go back to the Properties Portal instead of the report.

Recommended setup patterns

Good report use cases

Project trackers
Team directories
Asset lists
Release overviews
Meeting or decision indexes

Best design habits

Use clear field names
Prefer structured fields
Keep filters intentional
Limit visible columns
Use page hierarchies or labels consistently

If your report feels cluttered, the simplest fix is usually to reduce the number of displayed columns and use more specific filters.

Common issues and how to think about them

Check whether the selected property group is actually attached to pages and whether those pages match the configured filters. Also confirm that the report is pointing to the correct property group.

This usually points to a column configuration issue. Reopen the macro settings and confirm that the desired properties are included in Displayed properties.

First verify that the new page has the correct property group attached and that its values were saved. Then review report filters such as labels, spaces, or page location to make sure the new page matches them.

No. Start by creating and attaching property groups through the inline Properties experience and editor. Use the report after the structure is in place and multiple pages are using that same group.

Practical guidance

Start from a real use case such as tracking projects, approvals, or content ownership
Choose structured fields like select, date, people, and number when reporting matters
Keep reports focused by showing only the columns that support decisions
Use labels so filters stay reliable
Treat the report as a workspace for review and maintenance, not as the place to redesign schema

Overview of the Property Group Report