...

• Tag Type –The broad category of what the tag is about or the purpose the tag serves.
  E.g.: dissociate roles between “Agile” and “Traditional”, therefore creating a tag type as “Agile Role”.

• Tag Value –The label that fit under the broad category umbrella of the tag type.
  E.g.: Product Owner, Scrum Master, Transformation Leads.

...

Each simple tag created is associated to a given type but represented as a single data point based on its value. For example, Product Owner, Scrum Master and Transformation Leads are 3 separate tag values within the Agile Role tag type, hence represented as 3 separate individual tags.

...

Data stored as value with a common tag attribute will be applicable to all entities tagged with it. Hence changing the value of the attribute will update it for all groups, people or tag type associated with that tag attribute.

For example, people tagged as 2025 Graduate –a value for the Credential tag type– all share the same Completion Date as of March 31st 2024. If I update this completion date to April 1st 2024, all people tagged as 2025 Graduate will now have display this updated completion date.

To understand how to enable and bulk import tags with attributes refer to https://teamform.atlassian.net/wiki/pages/createpage.action?spaceKey=OS&title=Import%20Tags%20with%20attributes%20%28common%20attributes%29.

...

It is possible to make the information contained as the value of a tag attribute unique to the entity it labels. Which means that changing the value of the tag attribute will not change for all entities associated with it.

For example, two people can be tagged as Departing but have unique departure dates as attributes. Changing the date for one won’t affect the date of the other.

See also more information on how to Import Tags with Unique Attributes.

...

These tags cannot be edited in the App UI and need to be imported via integration.

...

.

...

Which source of truth for tags?

...