Training configuration

The training admin area is where competency requirements are set up — the courses that exist, who they’re assigned to, and the rules that make training mandatory. It’s the configuration behind the Training section.

The distinction that makes this a compliance control rather than an HR feature is enforceability. In a regulated environment it isn’t enough to offer training and hope people take it — you must be able to require specific competencies of specific people and prove, later, that the requirement was met. Marking an assignment mandatory and scoping it by project is what converts a good intention into an enforced, tracked obligation, so that when an inspector asks whether the people doing the work were qualified to, the answer is a record rather than an assurance.

Courses and assignments

You manage the catalog of courses and define assignments — who must complete which training. An assignment records who it was assigned by and can be marked mandatory for all assigned users, so a required course isn’t optional in practice. Training can be scoped and tracked by project, so the competencies a particular project demands are clear and managed in context.

Required training gates signatures

Mandatory training is enforced at the moment it matters: when someone signs. In a regulated project — or any project that turns on training required for approval or names its own required courses — a person must have completed the training that project requires before they can apply an electronic signature there: signing an approval step, a review decision, or a controlled transition. If anything is outstanding the signature is refused before the password is checked, and the message names the courses still to complete.

Which courses count is decided per project:

• A required course applies to the projects in its project scope. A course scoped to the aerospace project is required there and nowhere else; a course with no project scope is required in every project.
• A project can also name its own required courses, which apply there whatever their scope.
• Archived or inactive courses require nothing.

Completing a course is itself signed, and that signature is never blocked by this gate — a person can always sign off their own course, so working through the required curriculum one course at a time is possible.

Training settings

Broader training settings govern how the training program behaves across the organization — the defaults and rules that apply to courses, assignments, and completion. Setting these centrally ensures training is administered consistently rather than configured differently for each course.

Why it’s a compliance control

In a regulated environment, having the right people trained — and being able to prove it — is a compliance obligation, not an HR nicety. Configuring courses and mandatory assignments here is what turns “we should train people” into an enforced, tracked requirement. The user-facing side — taking courses, assessments, acknowledgments, and the analytics and audit trail behind them — is covered in Training.