Source: https://docs.amadalis.ai/site/taxonomies/

# Taxonomies, categories and tags

Checked against the product’s code on 7 November 2026.

Open **Site** > **Taxonomies**. This workspace manages EmDash’s native [categories](https://docs.amadalis.ai/reference/glossary/#category), [tags](https://docs.amadalis.ai/reference/glossary/#tag) and your own groupings. EmDash’s own sidebar entries for each taxonomy are hidden so there is one place to manage them. The categories, tags and groupings you see here are the same ones EmDash stores.

## Create a grouping

You need the Editor or Admin role to create a grouping.

1.  Choose **New taxonomy**.
2.  Enter its **Name**.
3.  Select the content types under **Applies to**.
4.  Choose **Shape**. **Flat** keeps values as peers. **Nested** permits parent and child values.
5.  Review **Key**. The key is the permanent name the site uses to identify the grouping; it stays fixed after creation.
6.  Review **One of them is called**.
7.  Choose **Continue**.
8.  Read the planned change.
9.  Approve the named action.

## Organize the values

1.  Open the grouping.
2.  Add a value using the add control, which uses the singular name you chose.
3.  Use that value’s actions to rename, describe, nest or reorder it.

**Remove** deletes a value: every piece of content filed under it loses that filing, and this cannot be undone. **Delete** at the top of a grouping removes the grouping, all its values and every filing under them; the content itself stays, and this cannot be undone either. Both pause for your approval. Renaming a value keeps every filing. **Move up** and **Move down** change their order. A nested grouping can assign a parent.

Changes to the grouping’s shape retain existing content filing links. They change how the values are organized, not which content has already been assigned to them.

## Read Catalog axis

**[Catalog axis](https://docs.amadalis.ai/reference/glossary/#catalog-axis)** reports whether the grouping is an interest category used by personalization. An unavailable reading is not the same as a known no. Creating a taxonomy alone does not configure every part of personalization.

Continue with [the content catalog](https://docs.amadalis.ai/optimization/affinity-engine/#build-the-content-catalog) when your published content and its tags are ready. Review the approval before making changes that affect an existing grouping.