Summary

Atlassian Guard Premium provides data classification for Confluence, but there is no native mechanism to require users to explicitly select a classification level before publishing a page. Classification can be applied automatically via defaults and automation, but this does not satisfy compliance requirements that mandate user-acknowledged data classification at time of authorship.

Org admins or space admins should be able to configure classification as a "required" field — similar to Jira mandatory custom fields — so that users cannot publish or save a page without explicitly selecting a classification level. This should apply to:

• New pages on creation
• Existing unclassified pages on first edit

Workaround

Third-party Marketplace apps can enforce this today, but cause double-classification when used alongside Atlassian's native classification UI.