--- title: "Tags" slug: "tags" description: "Create and manage tags in Slate to identify person and dataset records, configure tag settings, and set or unset tags." status: "update" updated: 2026-10-22T20:15:51Z published: 2026-10-22T20:15:51Z canonical: "knowledge.technolutions.net/tags" --- > ## 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 Record tags appear on the **Dashboard** tab of a [person record](/v1/docs/getting-started-with-records), a [dataset record](/v1/docs/datasets-overview), or [in the Reader](/v1/docs/reader-overview). They quickly identify important attributes about the record, like whether it is a test record, whether the record has opted out of communications, or whether they’re a VIP. Configure record tags in **Database → Tags.** ![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/Tags on the person record Dashboard tab.png?sv=2026-02-06&spr=https&st=2026-11-08T04%3A20%3A53Z&se=2026-11-08T05%3A20%3A53Z&sr=c&sp=r&sig=vEwzWv0DVn2bzG3L8Oiw1ce0eXtGRolCChElaaQXqgU%3D) ## Tags that come with your database Depending on the type of database you use, you’ll have the following tags by default: **Admissions 🪪** - **Test Record**: Label your test records to keep them separated from production workflows. - **Opt Out:** Indicates whether the record has opted out from marketing communications. The Opt Out tag has unique functionality. For more information, see [The Opt Out Tag](/v1/docs/the-opt-out-tag). **Student Success 🎓** - **Legacy Student:** An example of a tag that provides important context at a glance. - **Test Record**: Label your test records to keep them separated from production workflows. - **Opt Out:** Indicates whether the record has opted out from marketing communications. The Opt Out tag has unique functionality. For more information, see [The Opt Out Tag](/v1/docs/the-opt-out-tag). **Advancement 🤝** - **Test Record**: Label your test records to keep them separated from production workflows. In Slate for Advancement databases, you also have `Test Record` tags for the following datasets: - [Appeals](/v1/docs/store-appeal-data-in-a-dataset) - [Campaigns](/v1/docs/the-campaigns-dataset) - [Class Years](/v1/docs/the-class-years-dataset) - [Companies and Foundations](/v1/docs/companies-and-foundations-record) - [Educational Institutions](/v1/docs/the-educational-institutions-dataset) - [Funds](/v1/docs/funds-dataset) - [Performance Management](/v1/docs/the-performance-management-dataset) - **Opt Out:** Indicates whether the record has opted out from marketing communications. The Opt Out tag has unique functionality. For more information, see [The Opt Out Tag](/v1/docs/the-opt-out-tag). ## Where tags can appear in Slate Record tags can apply to person, application, or dataset records. Inbox uses separate tags for messages. ### Person record tags When you leave **Dataset** blank and select **Person** for **Scope**, the resulting tag appears on person records. Person tags can appear in the Reader if you select the **Show in Reader** setting when creating a new tag. ### Application record tags To create an application tag, leave **Dataset** blank and select **Application** for **Scope**. For a standard application tag, select **Normal** for **Type**. **Show in Reader** is not displayed for this scope. ### Dataset record tags To create a dataset tag, select the dataset and leave **Scope** set to **Person**. For example, select **Organizations** to create a tag for organization records. Set **Status** to **Active**, complete the remaining settings, and select **Save**. The tag appears on the dataset record’s **Dashboard** tab. ### Inbox message tags Use Inbox message tags to organize and filter messages. These tags are managed in Inbox, separately from the record tags configured in **Database → Tags**. For instructions, see [Inbox Overview](/v1/docs/inbox-overview). ## Creating a tag > [!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](/v1/docs/field-editor). Overpopulation makes tags less effective. Use these steps to create a person, application, or dataset tag. 1. Go to **Database** → **Tags**. 2. Select **Insert**. 3. Configure the following settings: - **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. - **Folder:** Keep tags organized in folders. Select *Other* and enter a name to create a new folder. - **ID**: Create a computer-friendly ID with all-lowercase letters and with no spaces, like `legacy`. 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**: Enter the tag’s human-friendly label, like `Legacy`. This may be updated, even if data already exists for the field. - **Dataset**: Add an optional dataset to include the tag in a dataset. - **Scope:** Select *Person* or *Application*: - **Person:** Associate the tag with a person record, or with a record in the selected dataset. - **Application:** Associate the tag with an application record. This scope displays the **Type** setting in the tag editor. - **Warning**: Enter an optional warning message that appears as a browser dialogue when the user sets or unsets the tag on a record. - **Order**: By default, tags appear in alphabetical order. Add an order to override this behavior. - **Group**: This field supplies a group heading for the deprecated Reader Annotation Shared Tags feature. Leave it blank for person and dataset tags. It does not organize tags on person or dataset record dashboards. - **Show in Reader**: For a person tag, select **Active** to show the tag when reading an application. This setting appears when **Scope** is **Person**. It is hidden when **Scope** is **Application**. - **Custom Read Permission:** Select a permission to restrict who can see the tag on person and dataset record dashboards. Leave this field blank to add no tag-specific read restriction. Users must still have access to the record. - **Custom Write Permission:** Select a permission to restrict who can select or clear the tag on the record dashboard. Users must also have permission to update the record. Leave this field blank to add no tag-specific write restriction. - **Rules Only:** Select *Administrative Updates Allowed* if users should be able to [set or unset the tag manually](/v1/docs/tags#setting-and-unsetting-tags). To prevent changes through the record dashboard, select *Updates via Rule Only*. - **Tag Tooltip:** Enter optional help text for the tag. Users can point to the tag on the record dashboard to read this text. Use **Warning** for a message that appears when a user sets or unsets the tag. 4. Select **Save**. ## Manually setting and unsetting tags To set or unset a tag on a record, select the tag name. A browser dialogue appears; confirm it to set (or unset) the tag. [![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/admin(1).png?sv=2026-02-06&spr=https&st=2026-11-08T04%3A20%3A53Z&se=2026-11-08T05%3A20%3A53Z&sr=c&sp=r&sig=vEwzWv0DVn2bzG3L8Oiw1ce0eXtGRolCChElaaQXqgU%3D)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/admin(1).png?sv=2026-02-06&spr=https&st=2026-11-08T04%3A20%3A53Z&se=2026-11-08T05%3A20%3A53Z&sr=c&sp=r&sig=vEwzWv0DVn2bzG3L8Oiw1ce0eXtGRolCChElaaQXqgU%3D) ## Inactivate a tag 1. Go to **Database → Tags** and select **Edit** for the tag. 2. Set **Status** to **Inactive**. 3. Select **Save**. The tag no longer appears on record dashboards. It remains in the configuration list. ## Delete a tag A [database administrator](/v1/docs/exclusive-permissions) can delete a tag from its **Edit** window. Deletion also removes the tag’s record assignments. The **Opt Out** tag is protected from deletion. To stop displaying a tag while keeping its configuration, set its **Status** to **Inactive**.