> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/entity-types/entity-type-custom-model/entity-type-custom-model-rename.md).

# Renaming or deleting a model-based type

## Renaming the entity type

To change the entity type name, on the entity type details page:

1. Click the actions menu next to the entity type name.

<figure><img src="https://3072847115-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvOPn7KQptPWmS5iKg5P0%2Fuploads%2FhVvc0W7iggl5DquOM6GQ%2FCustomEntityTypeModelOptionsMenu.png?alt=media&amp;token=3bf1bdc8-d7a3-4372-9750-9224ea838470" alt=""><figcaption><p>Actions menu for a model-based custom entity type</p></figcaption></figure>

3. In the menu, click **Edit entity name**.
4. On the **Edit Name** panel, provide the new name for the entity type.
5. Click **Save**.

## Deleting the entity type

You cannot delete an entity type that is enabled for any datasets. For information on how to enable and disable an entity type in datasets, go to [Enabling entity types for datasets](/textual/entity-types/enabling-entity-types-for-datasets.md).

To delete a model-based custom entity type, in the entity types list, click the delete icon.

On the confirmation panel, click **Delete**.


---

# 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.tonic.ai/textual/entity-types/entity-type-custom-model/entity-type-custom-model-rename.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.
