When to use Tag vs People Attributes

Owned by Space Sync for Confluence
Last updated: May 14, 2024

Sometimes data can be loaded into TeamForm as either a Tag or as an attribute linked to a person. This page lays out some considerations to help decide which to use.

(Note for advanced users - Tags can have attributes too)

Use Tags when 

Use Attributes when 

  • You want additional data (than built in TeamForm fields) visible in either Directory or TeamForm App  

  • You want users to be able to edit data from either Directory or TeamForm App (configurable) 

  • You want to allow users to navigate people or teams by the data

  • Multiple people need to view/ change the information

  • Data that is somewhat grouped with multiple people or teams having the same value. This allows the app to group them together (e.g. all the people with the tag value ABC)

Note: Tags can be bulk uploaded or added in app or directory.  

 

 

 

 

 

Recommended for (examples)

  • Job Architecture / Role type

  • Specialist Roles

  • Cost centre

  • Funding source 

  • The data is a foreign/external ID for the person or team (e.g. username, email address, Workday Org Unit ID)

  • Loading info into “in built” display fields in TeamForm (e.g. for people: name, band, reporting manager..., for teams: Team Name, members, associations, details, OKRs) 

  • You want to load data into TeamForm purely so it can be available via reporting/export data (visibility not needed in App or Directory)

  • Data that is largely unique values (e.g. username, email) where there is no need to group people or teams together by these data as no two people or teams will have the same data value.

  • Data that is hierarchal in nature (e.g. cost centre hierarchy). Attributes allows storage of hierarchal values (tags does not)

Note: personal attributes can only be bulk uploaded. May require a separate upload if data sourced outside the HR information system used to upload supply structure.

 

Recommended for (examples)

  • Most HR IS information (for visible fields)

  • Any information to be stored with a person or team, but which should not be displayed or edited via TeamForm

Examples

  • Job Architecture / Role type

  • Specialist Roles

  • Cost centre

  • Funding source 

Examples

  • Band (visible)

  • e.g. A source system team ID or person ID (not visible).

  • Username

  • Cost centre hierarchy