Tags

A tag is a single text label applied to a course. Tags do two things in Wisteria:

1. They trigger approval workflows. A course must have at least one tag to be submitted. Tags decide which workflow handles the review.
2. They carry recertification policy (roadmap). A tag will declare a recert interval that applies to every course wearing the tag.

This makes tags more load-bearing than the term suggests. They’re not free-form labels for organisation; they’re the binding layer between content and policy.

Creating tags

Super admins manage tags at Settings → Tags. Each tag has:

• Name — short text label
• Description — optional, helps trainers pick the right one
• Triggers workflow — which workflow(s) this tag activates on submit
• Recert required + Recert interval — optional; if set, every tagged course inherits (roadmap)

Plan your tag list as a small, finite set — typically 5–20 tags for a mid-sized organisation. The goal is for trainers to recognise the right tag instantly, not browse a long list.

Applying tags to a course

Trainers apply tags from Course Settings. A course can have multiple tags.

If a course has multiple tags pointing at different workflows, the strictest workflow wins (defined as the one with the most steps). The trainer doesn’t have to think about this — Wisteria computes it at submission time.

Why tags drive recert (not courses directly)

Two reasons:

1. Policy lives at the category level. “Annual safety refresh” is a policy that applies to many courses; encoding it on each course individually means changing the interval requires editing every course. Encoding it on a tag means changing one tag updates every tagged course.
2. Compliance audits ask category questions. “How do you ensure annual recert for safety training?” is easier to answer if your tag list is the answer (“here’s the safety-annual tag, here are all 12 courses using it, here’s each one’s most recent completions”).

Tag-driven recert is on the roadmap. For v1, recert is set per-course.

Renaming and deleting tags

• Renaming a tag changes its label everywhere; existing tagged courses keep the relationship.
• Deleting a tag unlinks it from every course. Any course that loses all its tags becomes un-submittable until a new tag is added.

A deletion confirmation dialog flags which courses are about to lose this tag, so super admins can decide whether to migrate them first.

Common tag patterns

For a regulated industry, a typical tag list might look like:

For a less regulated industry:

Audit trail

Every tag application, removal, rename, and deletion is recorded in the audit log. Filter the audit log by tag.* actions to see the full history of tag changes in your workspace.