Metadata for Confluence vs. Properties: 2026 Comparison

TL;DR

Both apps add structured metadata to Confluence Cloud pages, but they serve different purposes. Properties by Seibert – Junovi gives you the most field types and the most visual ways to view your data: boards, org charts, charts and inline editing. Metadata for Confluence by Elevatic is built for governance. You get required fields, dynamic default values, filtered page links, metadata sets tied to templates, category management you can hand to a group, and support for both Cloud and Data Center. For flexible, visual data, choose Properties. If you need structure your whole company sticks to, choose Metadata.

Availability and hosting

	Metadata for Confluence	Properties
Vendor	Elevatic, Platinum Marketplace Partner	Seibert – Junovi (Seibert group)
Hosting	Cloud and Data Center	Cloud only
DC → Cloud migration	✅ Metadata sets and descriptions migrate	– (no DC version)
Badges	Cloud Fortified · Bug Bounty	Cloud Fortified · Bug Bounty

If you run Data Center today, or you’re partway through a migration, Metadata is the only one of the two that covers both platforms.

What’s changed since our latest updates

Metadata for Confluence

• Default values for every field type. They can be fixed or dynamic (“Current user”, or “Current date” with an optional offset), and they apply whether a category is assigned through a template or manually.
• Link field filters limit which pages you can select by Content Category, by label, or both.
• Native page attributes in the Display Metadata macro: status lozenge, owner, creator, created on, last updated by, last updated on, and version.
• Faster Content Category loading when you browse and edit.
• Delegated category management: category owners can manage their categories without full admin rights.
• Multiple templates per category: a category can link to one template, several, or none.
• Current-user filter: the Report macro can show only the current user’s pages.
• DC → Cloud migration now includes set descriptions.

Properties

• New Charts view
• Attachment field type (July 2026)
• Field-level changelog (July 2026)

Feature-by-feature comparison

Capability	Metadata for Confluence	Properties
Text, single- and multi-select, user and date fields	✅	✅
Number, URL, email, phone, attachment fields	❌	✅
Colored select options	❌	✅
Page link field	✅	❌
Filter selectable pages by category or label	✅	❌
Required fields	✅	❌
Default values	✅ Fixed or dynamic	✅
Page status	✅ Native status shown in the page	✅ Status field
Show owner, creator, last updated and version	✅	–
Rename fields	✅	✅
Link to templates	✅ One, several or none	✅
Delegate category management without admin rights	✅	–
Restrict categories to users or groups	✅ via CC Managers group (delegated management)	✅
Category icons and creator audit	❌	✅
Report macro with label and space filters	✅	✅
Filter report by current user	✅	–
Card, board, org chart and chart views	❌	✅
Inline editing in reports	❌	✅
Show metadata values inside the page	✅	❌
Show values from other pages	✅	–
Copy metadata when you copy a page	✅	–
Field-level changelog and comments	❌	✅
Workflow automation	✅ via Workflows for Confluence (user field)	❌
Bulk edit in Cloud	❌	–
Native Confluence search by metadata value	❌	❌

Governance vs. flexibility

This is the real difference between the two apps.

Properties puts the user first. Teams get many field types, colors, and several ways to view and edit their data on the page. It works well for team wikis, HR directories and lightweight trackers, where the views matter as much as the data.

Metadata for Confluence puts the admin first. Admins define central field sets, attach them to templates, make key fields required and pre-fill them with defaults. A page can arrive already tagged with its author and creation date, and its links can only point to approved pages. Pages come out structured from the moment they’re created, without anyone cleaning up afterwards. For regulated, ISO-driven or public-sector teams, consistency matters more than views, and that’s what Metadata delivers.

Which one should you choose?

Choose Properties if you:

• Need many field types (numbers, URLs, attachments, colors)
• Want board, org chart or chart views and inline editing
• Run on Cloud only

Choose Metadata for Confluence if you:

• Need required fields, dynamic defaults and structure enforced from templates
• Want to control which pages users can link to
• Want category owners to manage their own fields without admin rights
• Are partway through a Data Center to Cloud migration and need continuity
• Want to trigger workflows from metadata