Overview

Organisations can issue temporary workforce credentials that prove role, training, and site clearance, then verify them at entry or system access points.

Why it matters

Short‑term staff create high onboarding overhead and risk. Credentials allow fast onboarding with clear expiry and revocation rules.

Ecosystem roles

  • Issuer: The employer or accredited training provider.
  • Holder: The contractor or temporary worker.
  • Verifier: Physical access systems and application services.

Assurance and lifecycle

Credentials should expire automatically at contract end and be revocable if training or clearance changes.

Objective Provide safe, time‑bound access for temporary staff.
Description Issue workforce credentials tied to role, site, and expiry.
Actors Employer; Contractor; Site operator
Dependencies Training and clearance data sources.
Preconditions Contractor is engaged and required training is completed.
Postconditions Access is granted within scope and duration.
flowchart LR
    EMP@{icon: "fa:building", label: "Employer", pos: "b"} -->|Issues workforce VC| WAL@{icon: "fa:wallet", label: "Wallet", pos: "b"}
    TRAIN@{icon: "fa:certificate", label: "Training provider", pos: "b"} -->|Issues training VC| WAL
    WAL -->|Present VCs| VER@{icon: "fa:id-badge", label: "Access control", pos: "b"}
    VER -->|Grant access| SITE@{icon: "fa:helmet-safety", label: "Site / system", pos: "b"}
sequenceDiagram
    participant Employer
    participant Trainer as Training provider
    participant Wallet
    participant Worker
    participant Access as Access control

    Employer-->>Wallet: Issue workforce VC
    Trainer-->>Wallet: Issue training VC
    Worker->>Access: Present credentials
    Access-->>Worker: Access granted or denied

You may also be interested in:

A practical, standards-aligned view of Verifiable Credentials for organisations building trusted ecosystems.