Skip to main content

Tags

Tags are labels you put on your members to organise them: by department, team, office, cohort, or any axis that matters to your organisation. A member can carry as many tags as you like.

Their main purpose: tags define the groups a manager is responsible for. A manager sees the assessments of the members of the groups they manage, so tagging is how you scope a manager's view to their part of the organisation.

How tags work​

  • A tag has a type (the axis, e.g. department, team, office, cohort) and a name (the value, e.g. Engineering, Madrid).
  • The type vocabulary is yours to define; use whatever axes fit your organisation. There's no fixed list.
  • A member can have many tags at once. Someone can be on the team: Platform, in office: Madrid, and part of cohort: 2026-H1 simultaneously.

Creating tags​

  1. Open Tags (People → Tags; admins only).
  2. Enter a type and a name and add the tag. Duplicate (type, name) pairs are rejected, so each tag is unique within your organisation.
  3. Deleting a tag also removes it from every member it was assigned to.

Assigning tags to members​

  1. Open Members and edit a member (admins only).
  2. Assign one or more of the tags you've already created; remove an assigned tag from the same place. New members can also receive tags from the invite link they joined through.

Set up your vocabulary first on the Tags page, then tag your members.

What tags do: manager scope​

Roles in Wiselook are admin, manager and member (Roles):

  • A member sees only their own assessments.
  • A manager sees the assessments of every member of the groups they manage, plus their own. Being in a group is not the same as managing it: a manager tagged team: Platform and office: Madrid who manages only team: Platform sees the Platform team, not the whole Madrid office.
  • An admin sees every assessment in the organisation.

Which groups a manager manages is set on the manager's member page: assign the tag, then mark it as managed. The same manager can manage one group and merely belong to another.

A worked example:

  1. Create team: Platform.
  2. Assign it to the members of that team, and to the manager, marking it as managed on the manager's page.
  3. The manager opens Evaluations and sees the team's assessments. Members you didn't tag don't appear; groups the manager belongs to without managing them don't either.

Managers can also invite new members straight into the groups they manage; see Managing members.

A note on widget visitors​

Tags apply to your members. They do not apply to widget visitors. People who take an assessment through a widget on your website have no member identity, so they belong to no group. Widget-visitor assessments appear only in an admin's Evaluations list, and drop out of it when it is filtered by a tag.