> 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/mark-a-schema-as-featured.md).

# Mark a Schema as Featured

Highlight a template schema so it stands out in schema lists and sorts first wherever it's listed.

Featuring a schema highlights it with a star and pins it to the top of every schema list it appears in. Use it to call out the schemas policy authors are most likely to need from a template. See [Schema Templates Concept](/docs/develop/guardian/workspace/schema-templates.md) for how the flag is stored and propagated.

### Prerequisites

* The user is signed in as a Standard Registry user.
* The user has permissions to manage schema templates.
* A draft schema template exists with at least one schema.

### Steps

1. Open the Schema Templates grid and open the template's editor.
2. Open the template's settings (the configuration step, not the schema editor).
3. Select a schema in the sidebar.
4. Click the star icon next to the schema name in the header.

   An outlined star means the schema is not featured. A filled, yellow star means it is. Clicking toggles between the two and marks the template as having unsaved changes.
5. Save the template.

   Saving writes `featured` into the template's configuration for that schema, and denormalizes it onto the schema itself as `templateFeatured`.

### Result

The schema shows a filled star, and sorts before non-featured schemas within the same topic, everywhere its template schemas are listed: the main Schemas grid (`/schemas`), the template editor's own schema sidebar, the template-scoped schema editor, and the policy schema editor for policies with this template applied. It also shows a filled star and sorts first in every policy configurator schema-picker dropdown (e.g. the Schema field on `Request VC Document`, `Document Validator`, and other blocks that let you select a schema), once the schema has been copied into the policy.

### Troubleshooting

**Why doesn't a policy's copy of the schema show as featured after I feature it in the template?**

Featuring a schema in the template does not push live to policies that already have the template applied - the same as every other template restriction. It takes effect the next time the template is applied to a new policy, or when an applied template is updated.

### Related

* Concept: [Schema Templates Concept](/docs/develop/guardian/workspace/schema-templates.md)
* Task: [Create a Schema Template](/docs/develop/guardian/workspace/schema-templates/create-a-schema-template.md)
* Task: [Apply a Schema Template](/docs/develop/guardian/workspace/schema-templates/apply-a-schema-template.md)
* Task: [Update an Applied Schema Template](/docs/develop/guardian/workspace/schema-templates/update-an-applied-schema-template.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guardian.hedera.com/docs/develop/guardian/workspace/schema-templates/mark-a-schema-as-featured.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.