How to modify tag type configurations
Configurations are settings that system admins can turn on and off as a way to control how a tag appears in TeamForm.
Before you turn start configuring a tag type, the tag type must already be created.
Note that any bulk import will import the tag regardless of the tag config (e.g it can put a tag against a team even if it is supposed to be a tag for people only).
Allow groups to have this tag type
When enabled this tag type can be linked to team structures.
When turned off users will be unable to select this tag type for linking to groups.
Turning this off will not unlink groups already tagged. The data will remain.
Use-Cases
Org Design: in vs out of scope teams and divisions, No fly zones, reviewed design, etc.
Add more classification to teams without needing to create different team types. For example on the team type ‘Agile Team’ allow tags that indicate ‘Platform team’, ‘Application team’ & ‘UX team’.
Tag applications supported by a team.
Allowed group types
Dependant on #Allow groups to have this tag type
Restricts which team types can be linked to this tag type. You can specify one or more team types which are allowed to be linked to this tag type.
Use-Cases
Only allow Agile Teams to be tagged with an Application tag. Crews and Domains cannot own an application.
Allow tag type as group association
If enabled, turns this tag type into a special two way tag type used to associate two teams together in some way.
Use-Cases
Allow Team A to be associated to Team B, this shows up in the associations tab of a Team.
The works like a Team to Team dependancy and a relationship defined for the association.
Allow individual to have this tag type
If enabled, tags of this type can be applied to individuals.
Turning this off will not disconnect groups already tagged. The data will remain.
Use-Cases
Pace roles
Skills synced from an external system.
Skills populated by users in the app.
Role impacts in an org design project.
Allow individual/group to have multiple tags of this tag type
If enabled, multiple tags of this type can be applied to teams and/or individuals.
Use-Cases
Individuals with multiple skills.
Multiple possible role impacts in an org design project.
Allow users to add new tag values
If enabled, users can create new tags of this type in the application.
Use-Cases
New Position Titles
Or any tags where free text should be enabled rather than a defined list of values
Show tag type in
Here you can specify where in the TeamForm app the tags of this type can be shown in the UI
Only a display control - does not prevent the data from reaching the user’s browser
Option | Explanation |
|---|---|
TeamForm | Shown in the TeamForm app |
Directory | Shown in the Directory |
Individual’s history |  Example of tag events shown in the individual’s history |
Navigation |  Example of the MISSION tag type in the Navigation Use-Cases
|
Applied count tooltip |  Example of applied count tooltip in the tags navigation Use-Cases
|
Skills requirements | This allows the tag type to become available in Planner for selection in the Requirements input box  Example of specifying Requirements using ROLE tags in Planner Use-Cases
|
Highlight as group badge
Use-Cases
Show the individual’s name who is the manager of particular teams.
Scope
Allow user to select this tag status:permissions
If enabled, users can select the tags of this type in the app.
Show removed tags
If enabled, users can see previously applied tags of this type in the app.
Use-Cases
If an individual is changing from one job profile to another in an org-design project, this will reveal the previous job profile for context.
Allow users to edit the value of tag
This will enable the edit pencil to show up for users to change the values of a tag, note that this will change the value of the tag everywhere it exists.
Use-Cases
Initiate a list of tags and delegate the continuous update of tags to multiple users
Highlight as person badge
Enabling this will mark this tag type as a special individual tag, which will be highlighted next to an individual's name.
Use-Cases
Reveal who in a team has a specialist role such as a Product Owner without having to consult each person’s page.
Read only
If enabled, tags of this type will only be read only hence users cannot add new tags, rename existing tags or remove a tag
Use-Cases
Data sync from external system (ex. Workday Skills)
Allow Admin to edit read only tags
If enabled, admins will be able to edit read only tags
Dependant on Read only
Allow Power User to edit read only tags
If enabled, power users will be able to edit read only tags
Dependant on Read only
Use-Cases
Enabling Leaders of People to assign & remove specialist roles from individuals. Directory users will see the specialist roles but will be unable to modify them.
Hide show info icon in tag display
If enabled, show info icon button will be hidden in tag display which means if additional data were stored within the tag, users cannot click on the info icon to read about about the additional data
Use-Cases
Hide attribute information modal (it will still be visible on the tag details page)
Hide tag type in tag display
If enabled, tag type label will be hidden in tag display
Use-Cases
Simple clean design.
Team Owner tag.
Hide long tag type names.
Tag values that are self-explanatory.
Related information