---
title: "Tags"
slug: "tags"
updated: 2026-04-03T00:00:02Z
published: 2026-04-03T00:00:02Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Tags

Tags appear on the **Dashboard** tab of a Record and are designed to identify populations at a high-visibility level. For example, setting the Test Record tag provides an easy way to identify records that were created to test your processes. Two tags are automatically included for Person Records in the Slate instance:

- Opt Out
- Test Record

The Opt Out tag has unique functionality. For more information, see [the Opt Out Tag](/v1/docs/the-opt-out-tag) article.

> [!TIP]
> ⭐ Best Practice
> 
> Tags provide a quick way to view or set high level information, but they should not be used in place of fields. Overpopulation of the Tags area makes these items less effective.

## **Creating a Person Record Tag**

1. Select **Database** on the top navigation bar and select **Tags**.
2. Select **Insert**.
3. Enter the following configurations in the popup window:
  - **Status**: Set the status to **Active**.
  - **ID**: Create an ID that is all lowercase letters with no spaces (for example, "legacy").
  - **Name**: This is the name of the tag that will appear on the **Dashboard** tab.
  - **Dataset**: Leave the Dataset field blank.
  - **Warning**: (optional) Enter a warning message that will appear when a tag is being administratively set or unset.
  - **Type**: Select Scope of **Person**.
  - **Order**: By default, tags appear in alphabetical order. Add an order to override this behavior.
  - **Show in Reader**: Set to **Active** (this allows for tags to be visible when reading application.)
4. Select **Save**.

## **Setting and Unsetting Tags**

To set or unset a tag on a record, all that is required is to click the tag on the right-hand side of the page. If the tag has a blue background, that means that Tag is set. If it has no background, that Tag has not been set.

[![Admin.png](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/admin(1).png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/admin(1).png)

## Tag Setting descriptions

| Setting | Description |
| --- | --- |
| **Status** | A tag that is no longer used should be set to Inactive. - **Inactive**tags are not displayed on the record or available for selection. - **Active**tags are displayed on the record and available for selection. |
| **ID** | This is the code that Slate will use to store fields in the database. It is best practice to create an ID in lowercase with no spaces or special characters other than an underscore. Once this ID is set and in use, the ID should not be changed. This ID is used to store data in the database, and is not a value that most administrative staff will see. |
| **Name** | Provide a display name for the tag. This may be updated, even if data already exists for the field. |
| **Dataset** | Optional: Add a dataset to include the tag in a dataset. |
| **Scope** | Select either Person or Application. - **Person**: this will associate the tag with the person record, showing the tag on the Dashboard of the person record. - **Application**: this will associate the tag with the application record and can be set via a Tag rule; the tag will show in the Reader. |
| **Warning** | Optional: Enter a warning message that will appear when a tag is being administratively set or unset. |
| **Order** | When configured, the tags will appear in the specified order. If left blank, the tags will be displayed in alphabetical order. |
| **Show in Reader** | This setting allows for tags to be visible when reading application. |