Adding & Removing Tags in Dasseti Engage

Tags in Dasseti Engage are labels used to organize, group, and filter content.
They are used across multiple Engage modules — including Requests, Companies, Products, Q&A Bank, and Files — and function the same way in each module, though screens and workflows differ slightly.

Tags are a classification tool — distinct from folders — and can be applied to many types of content.
For step-by-step instructions, see How do I add tags?
 

Contents

• Where Tags Are Used

• How Tags Work

• Adding Tags

• Renaming a Tag (Workaround)

• Removing Tags

  • Remove a tag from a single item

  • Remove a tag in bulk

• Best Practices

Where Tags Are Used

Tags are available across Engage modules that support content organization, including:

• Q&A Bank

• Requests

• Companies

• Products

• Files

Each module maintains its own independent tag list.
 

How Tags Work

Action	Behavior
Create a tag	Type a new tag name when tagging an item
Apply a tag	Attach a tag to an item (question, request, product, etc.)
Filter by tag	Use tags to narrow results in search or filters within that module
Rename a tag	❌ Not supported

 

Adding Tags

Renaming a Tag (Workaround)

Tags cannot be renamed directly. To change a tag name:

1. Add the new tag to items

2. Remove the old tag from those items

Once no items use the old tag, it disappears.

Removing Tags

Tags are managed through the items they are attached to — not from a central tag list.

Remove a tag from a single item

1. Open the item in edit mode

2. Locate the tag next to the content

3. Click the X on the tag

4. Save changes

The tag is removed from that item only.

Remove a tag in bulk

If a tag is removed from all items, it effectively disappears from that module.

There is no separate “delete tag” action. Tags only exist as long as they are assigned to at least one item. If needed again later, the tag must be recreated.

***Answer tags can only be bulk removed from the grid view***

Best Practices for Tags

• Use consistent naming conventions within each module

• Avoid near-duplicates (e.g., “Compliance” vs “Compliance-Related”)

• Use tags for filtering and grouping, not hierarchy