Create a Schema Template

Create reusable schemas and restrictions for draft policies.

Prerequisites

• The user is signed in as a Standard Registry user.
• The user has permissions to manage schema templates, schemas, and draft policies.
• A draft policy exists before applying a schema template.

Steps

1. Open the Schema Templates grid.

   The grid shows standalone schema template entities. It supports create, edit, import, export, publish, new version, delete, and filtering behavior consistent with Guardian grids.
2. Create a draft schema template.

   The template gets its own topic and is stored independently from policies. Draft template content is stored in MongoDB. Published template content follows Hedera/IPFS publication flow.
3. Open the template editor.

   The editor lets the user change the template name and description, create schemas for the template, and open template settings.
4. Create template schemas.

   Schemas created inside the template are saved with category = TEMPLATE, templateId, stable templateSchemaId, and field-level templateFieldId values.
5. Configure template restrictions.

   The supported settings are:

• Change schema settings (schemaSettingsLocked): locks schema name, description, and entity type.
• Can add custom fields (customFieldsLocked): prevents adding custom fields to the schema.
• Can edit selected field (fields[fieldId].locked): prevents editing and removing an individual template field.

  • Template-owned fields are locked by default; set locked: false explicitly to allow policy users to edit or remove the field.

Result

You have a draft schema template with reusable schemas and restrictions. You can apply it to an eligible draft policy.

Troubleshooting

Why can’t I edit a template field?

The template restriction can lock individual fields. Update the restriction before editing the field.

Related

• Concept: Schema Templates Concept
• Task: Apply a Schema Template
• Task: Import a Schema Template