> 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/custom-entity-types-list.md).

# Viewing the list of entity types

The **Entity Types** list displays the additional types that you created or imported, and provides access to the [list of built-in types](/textual/entity-types/built-in-entity-types.md).

To display the **Entity Types** page, in the navigation menu, click the entity types icon.

<figure><img src="/files/qjz4cBM7D1OxTDFeLxuc" alt=""><figcaption><p>Entity Types page</p></figcaption></figure>

## Information in the list <a href="#custom-entity-type-list-info" id="custom-entity-type-list-info"></a>

For each entity type, the **Entity Types** page includes the following information:

* Name of the entity type.
* For added model-based types:
  * The progression tracker. For more information, go to [Using the progression tracker](/textual/entity-types/entity-type-custom-model/using-the-progression-tracker.md).
  * The published model.
* Whether the type is an added regex type, an added model-based type, or a type that you imported from the entity type library.
* Whether the type is enabled for any datasets and if so, the number of datasets that it is enabled for. For more information, go to [Enabling entity types for datasets](/textual/entity-types/enabling-entity-types-for-datasets.md).
* When the type configuration was most recently updated.

## Filtering the list <a href="#custom-entity-type-filter" id="custom-entity-type-filter"></a>

You can filter the list by type name, by category, and by the user who created the type.

### Filtering by name <a href="#custom-entity-type-filter-name" id="custom-entity-type-filter-name"></a>

To filter the list by the entity type name, in the search field, begin to type text in the name. As you type, Textual filters the list to only include matching entity types.

### Filtering by category <a href="#custom-entity-type-filter-type" id="custom-entity-type-filter-type"></a>

To filter the list based on whether the entity is regex-based, model-based, or was imported from the library:

1. Click **Categories**.
2. Check the checkbox next to each source type to include.

### Filtering by creator <a href="#custom-entity-type-filter-creator" id="custom-entity-type-filter-creator"></a>

To filter the list to only include custom entity types that were created by specific users:

1. Click **Creator**.
2. In the dropdown list, check the checkbox for each user to include.

## Sorting the list <a href="#custom-entity-type-list-sort" id="custom-entity-type-list-sort"></a>

The entity types are always grouped by type. By default, within each type, they are sorted by name.

To reverse the order of the groups and names, click the **Name** column heading.

To sort by when the types were most recently updated, click the **Last Updated** column heading. To reverse the sort order, click the column again.


---

# 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://docs.tonic.ai/textual/entity-types/custom-entity-types-list.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.
