Assignment / Skills & Languages
Skills & Languages
Skill matching connects three things: a dropdown field on a workflow template, a set of skill values on a user's profile, and the assignment engine's filtering step that compares the two.
How a dropdown field becomes a skill field
Any Dropdown field on a stage's completion form (or on the ticket-level fields captured at creation) can be marked isSkillField: true when the template is configured — see Custom Fields. A "Language" dropdown with options like Hindi, Tamil, and Telugu is the most common example in media production templates, but the same mechanism works for any categorical requirement — market familiarity, content category, or platform specialization.
Tagging users with skills
On the user management side (see Managing Users), an admin assigns each user one or more skill values matching the same option sets used in skill fields — a writer might be tagged with language: Hindi and language: Tamil if they're capable in both.
How matching happens during assignment
When a ticket is created and its language field is set to, say, Tamil, and it reaches a stage with language marked as a skill requirement, the assignment engine filters the eligible pool down to only users tagged with language: Tamil. If the ticket had instead been created with Hindi selected, the same stage would resolve to a different, Hindi-tagged pool — the stage configuration doesn't change; only the ticket's own field value determines who's eligible.
Skill fields must be of type Dropdown. Text or Number fields can't currently be used as skill-matching criteria, since skill matching relies on comparing against a fixed, known set of option values.
This keeps one workflow template genuinely reusable across every language or market variant of a campaign, rather than needing a separate template per language.
Next: Roster & Shifts covers the "on shift, present today" layer of assignment filtering.