Tags

Record tags appear on the Dashboard tab of a person record, a dataset record, or in the Reader. 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.

Tags that come with your database

Depending on the type of database you use, you’ll have the following tags by default:

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.

Creating a tag

⭐ 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 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. 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.

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 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.