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. A tag scoped to a team is a team tag. A tag open to everyone is a Global Tag, and a tag imported from a data catalog is an External Tag. See Types of Tags for a side-by-side comparison.

What Team Tags Are For¶

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¶

Where	Who sees it
The Tags page, tag pickers, and tag filters	Members of the team and Admins.
An asset that carries it	Everyone who can open the asset.

Badges and the Scope field show a team tag with a team icon. Users outside the team see it on the assets that carry it with a lock icon instead, and can't apply or remove it. When they edit the asset's tags, the team tag stays in place. Hovering over the 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¶

Action	Who can do it
Apply or remove it on an asset	Members of the team, and Admins, with the team permission that lets them edit the asset. See Tag Permissions.
Create, edit, or delete it	Admins, and users whose team holds the Editor team permission. Any user role works.
Change its Scope	Admins only.

The Public team is the exception. Every user belongs to it, so its tags count as global, and only Admins manage them.

How a Tag Becomes a Team Tag¶

A tag is a team tag when it is created with a team as its Scope, from the Add Tag form or from a tag picker. 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.

Changing a Tag's Scope¶

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

Change	Effect
Global to a team	The tag is removed from every asset outside the team's datastores, archived ones included, and from check templates.
One team to another	The tag is removed from every asset outside the new team's datastores.
A team to Global	Nothing is removed. The tag becomes open to everyone.

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.

Removals are not undone

Making the tag global again later does not put it back on the assets it was removed from.

When a Team's Access Changes¶

Event	Effect on the team's tags
The team loses a datastore, whether it is removed from the team or the team is removed from the datastore	The team's tags are removed from that datastore's assets, archived ones included.
The team is deleted	Its tags become global and stay on the assets that carry them.

Weight and Scoring¶

A team tag carries a Weight Modifier like a global tag. 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 Weight Modifier.

Team Tags in Flows and Filters¶

Tag filters in a Flow's trigger or anomaly action, and in lists and Explore, only offer the tags you can use. Another team's tags already in a Flow's filter stay there when you edit the Flow.
An Archive action that adds tags gives each anomaly only the team tags whose team can access that anomaly's datastore.

Example¶

The finance data team wants a Q3 Close label for the tables it reconciles each quarter. A team Editor creates Q3 Close with the Finance scope and applies it to those tables. Only Finance members and Admins see it in pickers and filters, and other teams see it on the tables with a lock icon. After the close, the team deletes the tag on its own.

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.