Schema permissions
Control where schemas can be used and who can fill them in.
SCHEMA & GOVERNANCE
Eligibility
A schema can be restricted by Confluence spaces, page labels and groups. The capture and report macro only offer schemas that are eligible for the host page and current user.
Plan access before publishing
Use the schema permissions editor to keep sensitive schemas out of unrelated spaces. Test the macro with an intended author before rolling it out broadly.
How eligibility is evaluated
A schema can be limited by Confluence space, page label and group membership. The capture and report settings query only schemas that are eligible for the host page and current person, so restrictions apply before an author selects a schema.
Rules combine as safeguards: use the smallest scope that matches the workflow, then test both the intended page and an intended author or reviewer before publishing broadly.
Plan for moved pages
Eligibility depends on the current page context. If a page changes space or labels, recheck whether the schema should remain available there and whether reports should still include the page's entry.
Confluence governance
Check schema eligibility with an intended author before rollout. Space, label and group rules decide which schemas are offered on a page.
Result
Control where schemas can be used and who can fill them in.
Next step: Capture metadata on a page