Managers: For the full Solution options setup path (order of work and all tab groups), start at Managers / Solution options hub.
Portal path: /manager/solution-options?group=clinical&tab=clinical-documents
Navigation: Management → Solution options → group Clinical & governance → tab Clinical documents.
/my-certificates) to upload proof; this screen defines what types exist and who they apply to.When someone tries to book an available shift, the portal checks whether they still have mandatory clinical / governance documents missing. If anything is missing (with one exception below), booking is blocked with a message about compliance documents or certificates.
Staff can clear that by uploading valid documents on Certificates so they no longer appear as missing for their clinical grade and relationship (employment type), matching the rules configured here.
Exception: If a missing row is only “Due soon” (not fully missing yet), the shift booking check may still allow booking. (Exact behaviour comes from the database MissingRecords view used by the portal.)
| Field | What it means | How to use it |
|---|---|---|
| Name | The document name staff and managers see (e.g. “BLS”, “Manual handling”). | Required. Use clear, consistent naming. This is what appears on certificate lists and compliance views. |
| Grade | Clinical grade this requirement applies to. | Leave blank if the document applies to every grade. Set a value if only people with that clinical grade on their profile need this document. Must match how grades are stored on personnel records. |
| Relationship | Employment / relationship type (e.g. employee vs contractor). | Leave blank if everyone in the locale needs it. Set a value if only people with that relationship on their profile need it. Must match personnel Relationship values. |
| Driver | Marks the type as driver-related in reporting and ordering (e.g. recruitment document lists sort driver-related types). | Tick when the document is specifically for driver compliance; leave off for general clinical certs. |
| Governance | Flags the row as governance in the grid (column “Gov”). | Use for governance / policy-type certificates where you need that distinction in the matrix. |
| Non-expiring | Document type does not use a normal expiry cycle in the same way as time-limited certs. | Tick only when this type is not expected to expire; otherwise staff will supply an expiry when uploading. |
| Date active / Date inactive | The definition is only treated as active between these dates (inclusive), e.g. for recruitment wizard document lists. | Set so old types drop off automatically and new types have a clear start date. Outside that window, the type may not appear where “currently active” definitions are required. |
| ID (grid only) | Internal identifier; links uploaded Personnel documents to this type. | Do not change meaning casually: existing uploads reference Doc type = ID. Prefer editing a row rather than deleting and recreating if people already have uploads against that ID. |
Grid column shortcuts: Gov = Governance, Non-exp = Non-expiring.
| Audience | Where to go |
|---|---|
| Staff uploads | Profile → Documents → Certificates (/my-certificates) |
| Staff tasks | My tasks (/my-tasks), My compliance (/tasks/my-compliance) |
| Managers — compliance overview | Management → Workforce compliance (e.g. medic compliance, certificate validation) |
| Deep link to this tab | /manager/solution-options?group=clinical&tab=clinical-documents |
Docs/solution-options-manager.md