Team Tags¶

A Team Tag belongs to one team. Only that team's members can find it and apply it, and it only goes on assets in the datastores assigned to that team. Teams use them to label their own data without adding to the workspace-wide list every other team picks from.

Every tag has a Scope. Global tags are open to everyone. A tag scoped to a team is a Team Tag.

Why Use Team Tags?¶

• Team vocabulary: A team keeps its own labels, such as Q3 Close or Needs Backfill, without crowding everyone else's tag pickers.
• Self-service: Team Editors create and maintain their team's tags without waiting for an Admin.
• Clean boundaries: A team tag never lands on a datastore its team can't access, so the team can always see and clean up every asset that carries it.

Who Sees a Team Tag¶

Users outside the team see the tag on the assets that carry it, with a lock icon on its badge. They can't apply it or remove it. When they edit the asset's tags, the team tag stays in place.

Hovering over a team tag's badge shows its team and the note Only team members can apply or remove it.

Where a Team Tag Can Go¶

A team tag only goes on assets in datastores assigned to its team. This holds for everyone, Admins included.

• Applying it to an asset in another datastore is refused with a message saying the tag only goes on datastores assigned to its team.
• Check templates belong to no datastore, so they take no team tags.
• When an asset's tags are copied to another datastore, such as when promoting an asset or copying checks to another table, team tags whose team can't access that datastore are left out.
• Tag inheritance works as usual inside the datastore. A team tag on a datastore reaches its tables, fields, and checks.

Who Manages Team Tags¶

The Public team counts as global. Every user belongs to it, so its tags reach the whole workspace, and only Admins manage them.

A tag created by typing a new name on an asset, instead of from the Add Tag form, is always Global, so only Admins can create tags that way.

Weight and Scoring¶

Team tags carry a Weight Modifier like Global tags. It counts toward quality scores and check importance in the same way. Since the tag only sits in the team's datastores, its weight only moves scores there. See Tags Overview.

Tag Names Stay Unique¶

A tag name is unique across the whole workspace, whatever its scope. If another team already has a tag with that name, creating yours fails with a message saying the name already exists, even though you can't see that tag. Pick another name.

Changing a Tag's Scope¶

Admins change a tag's scope from the Scope field when editing it. See Edit a Tag.

Before saving a change that removes the tag from assets, the form shows how many assets lose it. Save stays off until you click Review, look through the assets in the Assets losing this tag dialog, and confirm. Nothing changes until you save.

When a Team's Access Changes¶

Team Tags in Flows¶

• Tag filters in a flow trigger or an anomaly action only accept tags you can use. Another team's tags already in a filter stay there when you edit the flow.
• An Archive action that assigns tags gives each anomaly only the team tags whose team can access that anomaly's datastore.

Key Takeaways¶

• A team tag is found and applied only by its team's members and Admins, but stays visible on the assets that carry it.
• It only goes on assets in datastores assigned to its team.
• Team Editors manage their team's tags. Global tags and scope changes are Admin-only.
• Restricting a tag to a team removes it from everything that team can't access.