> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/develop/guardian/workspace/schema-templates/apply-a-schema-template.md).

# Apply a Schema Template

Apply a reusable schema template to a draft policy.

### Prerequisites

* You are signed in as a Standard Registry user.
* You can update policies and read schema templates. Without both permissions the **Schema Templates** action does not appear.
* The target policy is a draft. It may already have other templates applied - a policy can have more than one template at the same time, as long as each is applied once.

### Steps

1. Open the **Policies** grid and find the target draft policy.
2. Select **Schema Templates** on that policy's row to open the management dialog.
3. Find the draft template or published template version under **Available templates**. Use the search box to filter by name; each row shows the template's version and status.
4. Select the apply action on that row.
5. Confirm when asked whether to apply the template to this policy.

The copy runs as a background task. Its progress screen reports when the schemas have been created.

### Result

The policy receives copies of the template schemas. The policy stores a template snapshot and binding.

### Troubleshooting

**Why is the Schema Templates action greyed out?**

The policy is not a draft. Only draft policies can gain, update or lose a template.

**Why is the template I want missing from Available templates?**

**Available templates** lists only draft and published templates that are not yet applied to this policy. A template that is already applied appears under **Applied templates** instead, where you can update or detach it. If the list is empty, every template you can see is already applied.

**Why was the apply rejected because of schema names?**

Two schemas in one policy cannot share a name, and applying a template copies its schemas in under their template names. The error names every clash and distinguishes the two cases: schemas that belong to another applied template ("Detach that template first") from schemas the policy already owns ("Rename or delete them first"), so it never suggests a detach that would not help.

**Why can't the policy be published?**

The policy is linked to a draft schema template. Publish the template first. You can also detach the template from the policy.

**Why are locked field controls unavailable?**

The applied template locks that field. Update the field in the template. Then apply the template update to the policy. Detach the template to remove all restrictions.

**Why can't I add a field?**

The applied template disables custom fields for this schema. Enable **Can add custom fields** in the template. Then update the policy. Detach the template to remove the restriction.

### Related

* Concept: [Schema Templates Concept](/docs/develop/guardian/workspace/schema-templates.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guardian.hedera.com/docs/develop/guardian/workspace/schema-templates/apply-a-schema-template.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.