We’re thrilled to introduce a highly requested feature to Metadata for Confluence Cloud: Required Metadata Fields in Content Categories
This feature is for teams struggling with missing data, unclear ownership, and messy documentation.
What exactly is new?
Admins can now:
- Mark key Metadata fields as required when setting up a Content Category.
- Change which fields are required anytime, without disrupting existing pages.
When users create a page or assign a category:
- Required fields show a red asterisk (*).
- The pagecannot be saved until all required fields are filled.
- If they close the dialog, the Content Category won’t be applied, keeping the system clean.
Why does this matter? (With real customer use case)
Let’s take a real example from a customer working with ISO 9001 process and policy management:
- Drafting stage: Someone starts creating a process or policy page in Confluence, but they don’t have all the metadata yet, maybe they’re waiting for the Process Owner’s name, Compliance Category, or Review Date. The page stays indraft mode as they gather the info.
- Finalization stage: Before the page is finalized and sent for management approval, the system requires those critical metadata fields to be filled. No more skipping key details or publishing incomplete documentation.
With required fields, there are more key benefits for your team:
- Stronger governance: Ensure critical fields like Owner, Description, Category, and Compliance Status are always set.
- Better compliance readiness: Perfect for teams working under standards like ISO 9001, where documentation completeness and traceability are essential.
- Less manual follow-up: Stop wasting time tracking down missing information or chasing page owners after the fact.
Want to give it a try? Update your current Metadata version or try it for free for 30 days!