Schema permissions

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.

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.

Public macro viewing does not enable anonymous access for a Confluence site or space. Configure public access in Confluence first, then publish the macro configuration. Both the host page and report source pages are checked for public readability on each request.

Schema space and page-label restrictions still apply. Anonymous and guest viewers cannot satisfy schema group restrictions on the public path. Public readers receive no access to schema discovery, administration, metadata writes or retained history. Test the published page while signed out before sharing it.

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.

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 metadata.