> For the complete documentation index, see [llms.txt](https://docs.lenses.io/latest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lenses.io/latest/devx/6.0/user-guide/schemas.md).

# Schemas

This page describes how to manage Schema in a Schema Registry with Lenses.

{% hint style="success" %}
To delete schemas you need to enable **`lenses.schema.registry.delete`** in **lenses.conf**.
{% endhint %}

## Creating schemas

To create a new schema, select **Environments->\[Your Environment]->Workspace->New Schema** and add your schema.

## Viewing schemas

To view the schema associated with a topic, select the **Schema** tab. Here you can view the schema for both the key and the value of the topic.

## Editing Schemas

To edit a schema select either the key or value schema. The schema editor will be expanded, click Edit to change the schema.

## Searching for schemas or fields

To list schemas go to **Environments->\[Your Environment]->Workspace->Schema Registry**. Lenses will show the current schemas, you can search in schemas for fields and schema names as well as filtering by format and tags.

## Evolving schemas

To evolve a schema, select the schema and select **Edit**. In the editor apply your changes. If the changes match the evolution rules the changes will be saved and a new version created.

## Changing compatibility

To change the compatibility of a schema, select the schema and from the actions menu select **Change compatibility**.


---

# 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://docs.lenses.io/latest/devx/6.0/user-guide/schemas.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.