> For the complete documentation index, see [llms.txt](https://help.tahua.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tahua.io/knowledge-base/administrator-help-guides/contracts/contract-templates/renaming-and-deleting-field-tags.md).

# Renaming & Deleting Field Tags

Once a Field Tag has been created on a form field (see [Personalisations & Field Tags](/knowledge-base/administrator-help-guides/contracts/contract-templates/personalisations-and-field-tags.md)), you can manage it centrally from **Settings > Tags**. This page lists every Field Tag currently in use across your Registration, Application, Assessment and Milestone forms.

#### How it works <a href="#how-it-works" id="how-it-works"></a>

* Go to **Settings > Tags**. You'll see a list of all existing Field Tags, with a search box to find a specific one.
* Next to each tag are **Rename** and a dropdown with **Delete**.

<figure><img src="/files/XNPk6FopnVhz89GvWeD1" alt=""><figcaption></figcaption></figure>

#### Renaming a tag <a href="#renaming-a-tag" id="renaming-a-tag"></a>

Click **Rename**, enter the new name, and save. This updates the tag everywhere it's assigned across your forms — any field currently carrying that Field Tag will now be associated with the new name.

**Important:** renaming does *not* automatically update the text you've already typed into your templates. If `[[your_field_tag]]` has been pasted into a Contract Template, Application Template, email template, or a report, that reference keeps pointing at the old name — it will stop pulling data through the moment you rename the tag, until you go into each place it's used and update it to `[[your_new_field_tag]]`.

Before renaming a tag, it's worth checking where it's currently used — Contract Templates, Application Templates, email templates, and any Reports/Data Tables built from it — so you can update those references straight away and avoid a gap where personalisations silently stop populating.

Tag names must be unique across your organisation, so you won't be able to rename a tag to something already in use elsewhere — you'll be prompted to choose a different name.

#### Deleting a tag <a href="#deleting-a-tag" id="deleting-a-tag"></a>

Open the dropdown next to **Rename** and select **Delete**. This removes the Field Tag from the field(s) it was assigned to. The form field itself isn't deleted — it just stops carrying that tag, and the personalisation is no longer available to insert into templates going forward.

**Repercussions to be aware of:**

* **Contracts and Applications:** any Contract Template, Application Template, or email template that already contains `[[deleted_tag]]` will keep the tag text in the template, but it will no longer resolve to a value. In line with how personalisations generally behave, it renders as blank rather than showing broken text — so documents will still generate, but that specific piece of information will be missing until the template is updated or the tag is recreated.
* **Reporting:** if the tag was used to power a column in a Report or Data Table (for example, to pull the same field across multiple form templates into one report), that column will stop returning data once the tag is deleted.
* **No warning is shown** before deletion about which templates or reports currently reference the tag, so it's on you to check usage first. Treat deletion as a one-way action for anything still referenced elsewhere.

#### Recommended workflow <a href="#recommended-workflow" id="recommended-workflow"></a>

1. Before renaming or deleting, search your Contract Templates, Application Templates, email templates, and Reports/Data Tables for the tag.
2. If renaming, update every reference to the new tag name as soon as you save the rename.
3. Only delete a tag once you've confirmed it's no longer referenced anywhere, or you're comfortable with those references going blank.

For the full list of built-in personalisation tags and how Field Tags fit alongside them, see [Contract Personalisations](/knowledge-base/administrator-help-guides/contracts/contract-templates/contract-personalisations.md) and [Personalisations & Field Tags (Applications)](/knowledge-base/administrator-help-guides/applications/application-templates/personalisations-and-field-tags.md). For how tags are used to combine fields across templates in reporting, see [How to pull fields from different forms into a single report](/knowledge-base/administrator-help-guides/reports/how-to-pull-fields-from-different-forms-into-a-single-report.md).