Credentials
What it's for
Credentials tracks the licenses and certifications your people hold — "Licenses & certifications tracked across your team". It is what Dispatch checks before it lets a technician take a job that needs a card, and what you show when a customer or an authority asks.
Reach it from People → Credentials in the sidebar, at /credentials.
Tabs
The screen has no tabs. Expiring and problem credentials get their own screen: the Compliance queue.
Panels and controls
- Columns: Credential, Holder, Number, Issued, Expires, and Status. Status is the whole point — a credential is useful only while it is current and verified.
- Adding a credential records the holder, the type, the number, who issued it, and the dates.
- Verify marks a credential as checked, with a note recording how — "Checked physical card" is the kind of thing that belongs there.
- Revoke takes a credential out of force and requires a reason, so a revocation is always explained — "e.g. AHJ notified us of revocation".
- Renew or replace issues a new number in place of the old one, keeping the history rather than overwriting it.
- Save evidence attaches the proof: a reference and a filename, e.g. card.pdf, or a link.
- No credentials on file is the empty state.
What it accepts
| Field | Format | Required | Rule |
|---|---|---|---|
| Holder | Pick a staff member | Yes | "Technician is required."; "Staff member not found in this org." |
| Credential type | Pick a type | Yes | "Please select a valid credential type." |
| Label / description | Free text — "e.g. Journeyman Card — WA State" | No | |
| Number | Free text — "License / cert #" | No | |
| Issuing authority | Free text — "e.g. WA State DOL" | No | |
| Jurisdiction | Free text — "e.g. US-WA" | No | What ties a credential to where it is valid |
| Issued / Expires | Dates | No | The expiry is what the compliance queue watches |
| Verification note | Free text | No | How the credential was checked |
| Revocation reason | Free text | Yes, to revoke | "A reason is required to revoke a credential." |
| New number | Free text | Yes, to renew or replace | |
| Evidence reference | A link or reference | Yes, to save evidence | "Evidence reference is required." |
| Filename | Free text — e.g. card.pdf | No |
How to configure it
- Compliance settings decide which credential types exist and which jobs require which cards.
- The Compliance queue carries its own alert threshold, which decides how far ahead an expiring credential is surfaced.
- Certification requirements set on job types are what Dispatch checks against when assigning.
Who can see it
This screen sits behind the Staff area.
Owners and office managers can open it. Dispatchers and technicians cannot — a technician's own cards are visible to them in the field app, but the whole team's credential file is an office record. The gate is checked on the server, not just hidden in the sidebar, so a direct link does not get around it.
The full role matrix is on Roles & permissions.