Skip to content

Trainings — Workflow

Overview

The Trainings workflow supports registering trainings and recording completion for collaborators through assignments. It provides a consistent way to maintain training records and attach proof documents (certificates) when required.

For the user-facing screen involved in this feature, see: Transactions.

Note

This feature follows SARA’s standard record lifecycle model.

See: Workflows & Pipelines


Roles involved

  • Human Resources (HR) / Administrators

    • Register and maintain trainings.
    • Assign trainings to collaborators and manage completion records.
  • Collaborators

    • Provide proof documents when required by policy (for example, certificates), typically through HR.

Status lifecycle

Trainings and assignments may use Active/Inactive states, depending on configuration.

Info

For system-wide status guidance, see: Status


Workflow

Workflow steps

  1. Create or update a training record
  2. Assign a training to a collaborator
  3. Add completion details and proof documents
  4. Maintain training and assignment records over time

Create or update a training record

HR creates a training with a code, name, and duration. Trainings can be updated as needed and deactivated when they should no longer be used for new assignments.

Assign a training to a collaborator

HR links a collaborator to a training through an assignment. This establishes the collaborator–training relationship used for reporting and tracking.

Add completion details and proof documents

If applicable, HR records a completion date and uploads one or more proof documents (for example, a certificate). Files can be replaced or removed when needed.

Maintain records over time

As policies or requirements change, HR can update training records, adjust assignments, and deactivate outdated items while retaining historical information for reference.


Setup & dependencies (Optional)

  • Collaborators must exist in SARA before trainings can be assigned.
  • If proof documents are required, define an internal policy for acceptable file types and retention.

Exceptions & operational notes (Optional)

  • Proof documents are optional unless required by your organization’s policy.
  • Deactivating a training prevents new assignments, but existing assignments remain available for reporting.

Permissions

Permissions

Access and actions are permission-driven.

See: Permissions