Requirement groups

Settings → People → Requirement groups is the list of groups that bundle related tags, such as skills or languages. Recruiters see these groups, with their tags, on a candidate and on a resource request. The groups are the organization's shared tag groups: the same groups are also offered wherever tags are applied to other records, such as invoices, projects and budgets.

Who can change it

The screen opens for people with the Candidates Manager permission, which administrators and HR managers have. Saving a group needs the Tags Manager permission, which administrators have and no default permission group includes. Someone who can open the screen without that permission will see their save refused.

The controls on this screen

The list shows each group by name. A group also shows its Code underneath, for example "Code" followed by a lowercase form of the name. The code is created from the name when the group is first saved and cannot be edited. Groups appear in the order set for them, and groups without an order sort by name. This screen does not reorder them. An empty list reads "No requirement groups yet." with the note "Ask an admin to configure requirement groups to add skills and languages."

Add requirement group: opens the Add requirement group dialog.

Edit: the pencil at the end of a row. It opens the Edit requirement group dialog.

Both dialogs hold the same field:

• Name: the group's name. Leading and trailing spaces are removed. The dialog cannot be saved while the name is empty.
• Cancel: closes the dialog without saving.
• Add: shown on a new group. Creates it. A group created here is not limited to particular kinds of record.
• Save: shown when editing. Stores the new name.

The Recommendations panel beside the list gives three tips: Group requirements, Share across job offers and Mark what's critical. They are advice only and hold no controls; a button on the panel, named Compact or Expand for screen readers, folds the panel away or opens it again. The group itself has only a name and a code. It has no field to flag a requirement as critical.

There is no control to delete a group.

Example use cases

• An administrator adds a "Languages" group so candidates can be tagged with the languages they speak.
• An administrator adds a "Technical skills" group and recruiters tag candidates against it.
• An administrator renames a group after the team agrees a clearer term.
• An administrator checks a group's code before building a report on it.