> 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/guardian/workspace/schema-templates/detach-a-schema-template.md).

# Detach a Schema Template

Remove a schema template binding from a draft policy.

Detach a template when the policy needs independent schemas. See [Schema Templates Concept](/docs/develop/guardian/workspace/schema-templates.md).

### Prerequisites

* You are signed in as a Standard Registry user.
* You can manage draft policies.
* The policy is a draft with an applied schema template.

### Steps

1. Open the draft policy with the applied template.
2. Select **Detach Schema Template**.
3. Review the removal warning.
4. Confirm the detachment.

### Result

The policy retains its schema copies. The template metadata and binding are removed. The schemas become editable.

### Troubleshooting

**Why is Detach Schema Template unavailable?**

Only draft policies with an applied template can be detached.

**Why can't I delete a schema?**

The schema belongs to an applied template. Detach the template first. The copied schema then becomes independent and editable.

### 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/guardian/workspace/schema-templates/detach-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.