S
Simpleasyty
Help Center — Page Properties
GETTING STARTED
IntroductionInstall the appQuick startRuns on Atlassian
SIMPLE TABLE
PasteAttachmentsFile uploadJoin tablesPage PropertiesConfluence ContentJira Issues
TABLE WITH BODY
Native Confluence tables
DATA STORAGE
Data residencyNo data egressSave table data
REUSE TABLES
Table Excerpt / Include
DISPLAY
SearchFiltersSortingGroupingRow numbersFull screen modeDownload tableConfidential labelRovo
COLUMNS
ReorderingRename headingHideIncognito modeText appearanceColumn colorsData typeGrouping aggregationFooter aggregationCalculated columnExpression functionsNested JSON fieldsDelete column
PIVOT TABLES
Overview
FORMATTING
Layout & spacingTable colorsTable heightPagination

Page Properties

Turn structured information across many Confluence pages into one live table. It is ideal for project portfolios, decision logs, or request registers where every page carries the same important fields.

SIMPLE TABLE MACRO

ONE ENTRY PER PAGE. ONE TABLE FOR THE OVERVIEW.

Turn scattered Confluence pages into a usable view.

Simple Tables finds matching pages, reads their Page Properties macro, and turns key/value data into table columns you can choose.

A deliberate scope

Choose one space and one label so every report has a clear, intentional boundary.

Fields discovered for you

Property keys across the matching pages become columns you can select and arrange.

Current when it matters

Values you already selected are read again from the current pages whenever the table loads.

Build a live overview

Each row represents one matching Confluence page. The Page Properties table on that page supplies the fields for the row.

1

Choose Page Properties

Add a Simple Table macro, open Integrations, and select Page Properties.

2

Set a clear scope

Choose exactly one space and one label, then select Get data. Simple Tables automatically narrows the search to pages with a Page Properties macro.

3

Choose the fields

Review the property keys it finds and select the fields that should appear as columns. Then configure and publish the table as usual.

Example: a project portfolio without a separate list

Each project has its own Confluence page, with status, owner, start date, and budget in Page Properties.

On project pages
Teams maintain the information where project work happens: one page for each project.
In the portfolio
One Simple Table reads every page with the label “project” and shows status, owner, and budget in a filterable, sortable overview.

What happens when pages are read

The source uses only pages that match both the selected space and label. It reads the native Page Properties macro; the separate Page Properties Report macro is not a data source.

Updates and limits

  • The scan processes up to 1,000 matching pages and shows progress plus information about skipped pages.
  • Native Confluence statuses remain statuses. Consistently detected dates and numbers keep their appropriate column type; mixed values remain text.
  • When a source page changes a value you already selected, the published table reads the current value when it loads.
  • New property keys are not added as new columns automatically. Open settings, choose Columns, and add the new field.