Global Tags¶

A Global Tag is open to the whole workspace. Every user can find it in tag pickers and filters, and it can go on any asset, in any datastore. Global tags hold the vocabulary the whole organization shares, such as PII, Finance, or Deprecated.

Every tag has a Scope. A tag whose scope is Global is a global tag. A tag scoped to one team is a Team Tag, and a tag imported from a data catalog is an External Tag. See Types of Tags for a side-by-side comparison.

What Global Tags Are For¶

Shared vocabulary: Every team labels its data with the same tags, so PII means the same thing on every datastore, check, and anomaly.
Platform-wide scoring: A global tag's weight reaches every asset that carries it, in every datastore.
Cross-team automation: Flows, saved filters, and operations that filter on a global tag cover every team's assets that carry it.

Who Sees a Global Tag¶

Where	Who sees it
The Tags page, tag pickers, and tag filters	Every user.
An asset that carries it	Everyone who can open the asset.

Badges and the Scope field show a global tag with a globe icon.

Where a Global Tag Can Go¶

A global tag goes on any datastore, table, file, field, check, check template, or anomaly, in any datastore. It is the only kind of tag a check template takes, since a template belongs to no datastore.

Who Manages Global Tags¶

Action	Who can do it
Apply or remove it on an asset	Anyone with the team permission that lets them edit the asset. See Tag Permissions.
Create, edit, or delete it	Admins only.
Change its Scope	Admins only.

Tags of the Public team count as global. Every user belongs to Public, so its tags reach the whole workspace, and only Admins manage them.

How a Tag Becomes Global¶

A tag is global when an Admin creates it with the Global scope. A tag can also become global, or stop being global, later:

Change	Effect
An Admin changes a team tag's scope to Global	Nothing is removed. The tag becomes open to everyone.
An Admin restricts a global tag to a team	The tag is removed from every asset outside the team's datastores, archived ones included, and from check templates. Making it global again later does not put it back.
A team is deleted	Its tags become global and stay on the assets that carry them.
A tag is named for the first time while an asset is tagged through the API	The new tag is created as global, so only Admins can create tags that way.

See Changing a Tag's Scope.

Weight and Scoring¶

A global tag carries a Weight Modifier that counts toward quality scores and check importance in every datastore where it is applied. Because one change reaches the whole workspace, only Admins change it. See Weight Modifier.

Global Tags in Flows and Filters¶

Every user can pick a global tag in a Flow's trigger or anomaly action filters, and in the filters of every list and Explore.
An Archive action can add a global tag to the anomalies it archives, in any datastore.

Example¶

A data governance lead wants every team to flag personal data the same way. An Admin creates a global PII tag with a weight of 8, and each team applies it to the fields and tables that hold personal data. One Flow filtered on PII now alerts the privacy team on anomalies from every team's datastores, and the tagged checks rank higher in every anomaly list.

Key Takeaways¶

A global tag is open to every user and can go on any asset, check templates included.
Only Admins create, edit, delete, or re-scope global tags, because their weight reaches the whole workspace.
Restricting a global tag to a team removes it from everything that team can't access.