Skip to content

Tag Permissions

Tag permissions follow two separate rules:

  • Applying a tag to an asset follows the asset: you need the team permission that lets you edit that asset on its datastore.
  • Managing a tag (creating, editing, merging, or deleting it) follows the tag's scope: global tags belong to Admins, and a team's tags also belong to the users whose team holds the Editor team permission.

Every user role can see the Tags list, open a tag's page, and see the tags on the assets they can access.

Legend:

  • The permission grants the ability to perform the action
  • The permission does not grant the ability to perform the action

Team Permissions

These apply per datastore. A user holds the team permission of the teams they belong to on that datastore.

Action Reporter Viewer Drafter Author Editor
See the tags on the datastore's assets
Apply or remove a tag on the datastore, its tables and files, and its fields
Apply or remove a tag on Draft checks
Apply or remove a tag on Active checks
Apply or remove a tag on anomalies
Move or remove a tag from the tag's page 1
Create, edit, and delete the team's own tags 2

With the Author team permission, the owner of a computed table, computed file, or computed field can also tag it.

Applying a team tag also requires being a member of its team, and the asset must be in a datastore assigned to that team. External tags are applied and removed only by the data catalog sync, whatever the permission.

User Roles

These apply across the whole workspace.

Action Member Manager Admin
See the Tags list and open a tag's page
Apply or remove a tag on check templates
Create, edit, and delete global tags
Create, edit, and delete any team's tags
Set the category and weight of an external tag
Change a tag's scope
Merge a tag into another 3
Find and apply another team's tags

Admins bypass every team-permission check. Managers do not: a Manager still needs the team permission shown above for the asset, and has the same rights as a Member over tag definitions, which are the tags of the teams where they hold Editor.

Module Requirements

The tag's page is open to everyone. Its Assets and Map tabs, and the Move to, Remove, and Merge actions, need the Data Catalog module. See Module Availability.

See Also

  • Introduction

    What tags are and why to use them.

    Introduction

  • How It Works

    How tags influence Qualytics, the three types, and how a tag spreads through a datastore.

    How It Works

  • Weight Modifier

    How a tag's weight changes quality scores and check importance.

    Weight Modifier

  • Global Tags

    Tags open to the whole workspace, managed by Admins.

    Global Tags

  • Team Tags

    Tags scoped to one team, and what happens when the scope changes.

    Team Tags

  • External Tags

    Tags imported from a connected data catalog.

    External Tags

  • Tag Page

    The summary, timeline, assets, and map of a single tag.

    Tag Page

  • Examples

    Real scenarios showing tags at work.

    Examples

  • Best Practices

    Guidelines for a small, consistent tag library.

    Best Practices

  1. Requires the Data Catalog module. The action only reaches the assets you could tag yourself under the rows above, so a Drafter moves or removes the tag on Draft checks only. ↩

  2. Held through the team itself, not a datastore. It applies to every user role, and never to the Public team, whose tags count as global. ↩

  3. Requires the Data Catalog module. ↩