S
Simpleasyty
Help Center — Schema permissions
GETTING STARTED
IntroductionQuick start
CREATE A SCHEMA
Create a schema from a templateCreate a schema from scratch
SCHEMA TEMPLATES
Security Risk RegisterISO 27001 Document ControlSOC 2 Evidence RegisterPolicy ManagementThird-Party RiskData ClassificationApplication PortfolioControlled DocumentArchitecture Decision RecordInformation Asset RegisterBusiness Continuity RegisterGDPR Processing Activity
IMPORT
Import a JSON or YAML schema packageImport Page Properties
FIELD TYPES
Schema field typesText fieldsNumber fieldsYes / No fieldsSingle choice fieldsDate / Time fieldsEmail fieldsURL fieldsConfluence reference fieldsList fieldsField group fields
MANAGE SCHEMAS
Manage schemasIndexed fields and filtersSchema permissions
CAPTURE DATA ON PAGES
Capture metadata on a pageCapture, validate and repair metadata
CREATE REPORTS
Build a Metadata ReportConfigure report filters and viewer controls
STORAGE & PRIVACY
Data residencyStorage in ForgeRetention and deletion
COMPLIANCE
Compliance workflowsMetadata, history and revisions
ADMINISTRATION & TROUBLESHOOTING
Import and exportSchema reconciliation and processesSecurity, storage and limitsTroubleshoot schemas, filters and reports

MANAGE SCHEMAS

Schema permissions

Control where schemas can be used and who can fill them in.

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