S
Simpleasyty
Help Center — Page Properties
INTRO
IntroductionInstall the appQuick startRuns on Atlassian
DATA PERSISTENCE
No data egressData residency
DATA SOURCES
Data sourcesImported dataSave as AttachmentConfluence ContentPage PropertiesNative Confluence tablesTable Excerpt / Include
DISPLAY
Display settingsSearchFiltersSortingGroupingRow numbersFull screen modeDownload tableConfidential labelRovo
COLUMNS
ReorderingRename headingHideIncognito modeText appearanceColumn colorsData typeGrouping aggregationFooter aggregationCalculated columnExpression functionsUse casesNested JSON fieldsDelete column
PIVOT TABLES
Overview
FORMATTING
Layout & spacingTable colorsTable heightPagination

Page Properties

Use Page Properties to turn matching Page Properties macros into one live Simple Table. It is useful when each project, request, or record has its own Confluence page and a key/value table describes that page.

Required search scope

Select exactly one space and one label. Simple Tables scans only pages matching both filters, then reads the Page Properties macro on those pages. Page Properties Report is not used as the data source.

Create a Page Properties table

  1. Insert a Simple Table macro or edit an existing one.
  2. Choose Integrations, then select Page Properties.
  3. Choose one space and one label, then select Get data.
  4. Review the discovered fields, select the columns to display, and continue to table setup.
  5. Configure the table and publish the page.

What Page Properties searches

The search controls are intentionally narrower than Confluence Content. Page Properties requires one Space and one Label; the label selector is single-select so every scan has one bounded scope. The app adds type=page and macro=details automatically.

It does not use the Page Properties Report macro as a source. It finds matching pages, reads the Page Properties macro body on each page, and combines the key/value rows into fields.

How fields are discovered

Each matching page must contain an identifiable Page Properties macro with a key/value table. Simple Tables combines property keys found across the matching pages into fields you can choose as columns. The scan has a safety limit of 1,000 pages; narrow the scope with a label that identifies the pages for your report.

Types are detected conservatively: native dates become Date, native Confluence statuses become Enum, consistently numeric values become Number, and mixed or other values remain Text. The scan reports progress, skipped pages, and diagnostics when a matching page has unsupported or invalid macro data.

Update values and add new fields

When you change a field already selected in the table, the macro reads the current Page Properties data when it loads and shows the updated value.

New key/value rows are not added to an existing table automatically. Reopen the macro settings, go to Columns, select Add columns, and choose the newly discovered field. This keeps control of the schema and layout with the editor.

Good practices

  • Use the same label on every page you want in the report.
  • Keep common property names consistent across pages.
  • Use a native Confluence status for controlled status values.
  • Use normal Simple Table settings for sorting, filtering, grouping, formatting, and calculated columns after choosing fields.

For a table that enhances an existing native table on one page instead, see Native Confluence tables.

Permissions and data handling

The table respects Confluence permissions for the person viewing it. Data is processed within Atlassian through Forge; see No data egress for details.

Want to try it in your site? InstallSimple Tables for Confluence from the Atlassian Marketplace.