Tags

Tags are how Zunderwork knows who belongs to what. They look like labels, but they do real work: a course reaches the people who carry the same tag as the course. Someone who has no tags sees no courses, and a course without a tag reaches nobody.

You manage them under Organization, Tags.

#Creating a tag

Choose Add tag and fill in what the tag stands for.

• Tag name: what people in your organization would call this group. This is the name you pick from everywhere else, and the name the CSV import matches on, so keep it short and unambiguous.
• Description: optional, but useful once you have more than a handful. Write down who belongs in this tag, so the next administrator does not have to guess.
• Color and Icon: how the tag looks in lists and on cards. Pick one of the presets, enter your own hex code, or use Random color if you do not care.
• Parent tag: optional, see below.

#Grouping tags together

A tag can sit underneath another tag, which keeps a long list readable: "Amsterdam" and "Rotterdam" under "Locations", "First aid" and "Forklift" under "Certifications".

Two limits are worth knowing before you plan a structure around this.

The tree is also only one level deep. A tag that already has a parent cannot become a parent itself, so you get groups and tags inside them, and no deeper nesting.

#Ways to use tags

There is no right structure, and Zunderwork does not impose one. What works depends on how your training is organised. Common approaches:

• By department or team: Sales, Warehouse, Care team. Fits when courses follow the org chart.
• By role or function: Driver, Forklift operator, First aider, Manager. Fits when the same training applies to people across several departments.
• By location or branch: useful when rules differ per site, or when you report per site.
• By intake group or class: New hires 2026, January group. Fits when a group goes through a programme together and the deadline should run from their start date.
• By status: Contractor, Temporary staff, Onboarding. Fits when a group gets a smaller or a different set of courses.

Most organizations end up combining two of these, for example a department tag plus a role tag, and let people carry both. That is fine: a person can have as many tags as you like and sees everything that any of their tags reaches.

What to avoid is a tag per person or per course. That works for a week and becomes unmanageable by the end of the year.

#Giving someone a tag

There are three moments to do this.

• On a user: open the person under Organization, Users and set their tags there. This is also where you correct a mistake.
• When you invite someone: the invite dialog lets you pick tags right away, so the right courses are waiting the moment they log in for the first time.
• When you import a list: the CSV import has a Tags column and matches on the tag name, exactly as you typed it in Zunderwork. You can also set tags that apply to everyone in the file.

In the users list you can filter on tags, which is the quickest way to check who is actually in a group before you attach a course to it.

#Renaming and editing

Renaming a tag is safe. It is the same tag everywhere, so people keep their courses and only the label changes. The same goes for a new colour, icon, description, or parent.

The one thing to watch is your CSV import files: those match on the tag name, so an import that still uses the old name will no longer find the tag.

#Deleting a tag

Deleting removes the tag from everyone who has it.

If your goal is only to stop a course from going to a group, remove the tag from that course instead. That leaves the tag, and everything else it does, intact.