nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Page Properties macro for Confluence Cloud?

William Rudy

I see this mentioned on this forum, but cannot find it (somewhere to obtain) anywhere on the internet. If there is a Page Properties macro for the Cloud version, can someone point me to it…and please don't point me to "Content Properties" as that is not the same thing. Thanks!

Accepted answers

All comments

Mia Tamm _Simpleasyty_

Hi @William Rudy,

I think I understand what you mean, especially your point that Content Properties isn't the same thing as the Page Properties workflow you're looking for.

If your goal is to attach structured fields to individual Confluence pages and then report on that metadata across multiple pages, we've actually been working on exactly this problem with Simple Metadata for Confluence.

You define a schema with the fields you need, apply it to pages, and then use the Metadata Report macro to collect and report that information across Confluence.

Full disclosure: I'm part of the team behind Simple Metadata, so obviously I'm biased 🙂 But if you can share a little more about what you were doing with Page Properties, I can tell you whether it would actually cover your use case or not.

Rick Westbrock

I think this might be one of the Confluence Server/Data Center macros that just isn't available in cloud based on what I remember from our migration from Server to Cloud back in 2022 or so.

William Rudy

Hi and thanks, but I don't think that would work. I'm looking for something that works just like the Page Properties macro does.

Mia Tamm _Simpleasyty_

Thanks for clarifying, @William Rudy!

Just to make sure I understand, are you looking for the exact same experience as the original Page Properties macro, including the ability to edit a simple key-value table directly on the page?

I ask because there are a few differences between that approach and schema-based metadata, and I wouldn't want to recommend something that doesn't fit your workflow.

Arkadiusz Wroblewski

Hello @William Rudy

Native Content Properties macro basically replaces a lot of the old Page Properties features, but there are a few differences. Cloud doesn’t handle tables that have both header rows and columns. Atlassian is tracking this issue under CONFCLOUD-82829.

Is that one of the differences you're referring to, or is something else missing from your original setup?

A screenshot would help us narrow it down. 🙂

Best,

Arek🤠🧙‍♂️

Mia Tamm _Simpleasyty_

Hi @William Rudy,

One other option came to mind that might be closer to what you're looking for, especially if you prefer the simplicity of the original Page Properties approach rather than managing metadata schemas.

You could keep things quite simple with Simple Tables for Confluence:

On each page, add a Page Properties (Content Properties in Cloud) macro and create a regular two-column table with your fields and values, such as Project, Owner, Status, and Due Date.
On your reporting page, insert the Simple Table macro.
Select Page Properties as the data source and configure which pages and fields you want to include.
You'll get a consolidated table that you can search, sort, filter, and export.

There's also a second macro called Simple Table Bodied, which works directly with native Confluence tables. That can be useful if you simply want to maintain editable tables on individual pages without introducing metadata schemas.

The main difference is that Simple Tables focuses on working with and reporting on existing tables, rather than managing structured metadata.

Full disclosure again, I'm part of the team behind it, but I thought this might be a simpler alternative for your use case.

We've put together a working demo showing how Page Properties can be used with Simple Tables:

https://simpleasyty-demo.atlassian.net/wiki/spaces/TABLEDEMO/pages/134053912/Page%2BProperties

Hope this helps! And if this isn't quite what you're looking for, I'd be happy to understand what's missing.

Monika Ambrozowicz_Seibert_

Hi @William Rudy, unfortunately the Page Properties macro is the Cloud version of Page Properties on Server/Data Center, I don't think you can find something else in native Confluence. It is also true that it is limited, it's a simple small table with no field types, no dropdowns, no date pickers, no user pickers… If you are open to a marketplace app, I'd strongly suggest looking at Properties.

The app lets you define reusable "Property Groups" - bundles of typed fields (text, dropdown, multi-select, date, user picker, status) that you build once and apply consistently across pages and templates. There is also a Property Report macro that aggregates those values from pages across your space (or across multiple spaces) into a filterable, sortable table, with inline editing directly from the report.

The overall pattern with structured metadata on individual pages, rolled up into a report elsewhere, is exactly what the classic Page Properties + Page Properties Report combination did on Server, but with typed fields, reusable schemas, and inline editing on top.

Full disclaimer: I am affiliated with the team behind the app. But it also means that if you have any questions I'm happy to help you, or show you around.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence-cloud

page-properties-macro