Skip to main content

Custom Credentials

A custom credential is a credential type your organisation defines itself, for something Oho doesn't have a built-in type for — an internal compliance course, a First Aid certificate, a forklift licence, a company induction. It sits alongside the catalogue credentials (Working With Children Checks, NDIS Worker Screening, AHPRA, and the rest) everywhere credentials are recorded, but with one important difference.

How they differ from verifiable credentials​

Most credentials in Oho are verifiable — Oho confirms them against the official register or issuing body and re-checks them on a schedule. A custom credential has no register behind it, so it is tracked manually: Oho records it, monitors its expiry, and surfaces it on your dashboards, but it can't confirm the document is genuine. Every custom credential is marked Not verified as a reminder that a person is responsible for checking it.

So the choice is simple: if a built-in type exists for what you need, use it and get real verification. Reach for a custom credential only for the things the catalogue doesn't cover.

What a custom credential can carry​

Each custom type is defined by an Admin and can hold:

  • a name and an optional description;
  • an expiry behaviour — a date entered per credential, an expiry calculated from an attainment date plus a validity period, or no expiry at all;
  • an optional attachment requirement (a scan or photo of the document); and
  • any number of custom fields — text, number, date, yes/no, or a dropdown of set options — captured on every credential of that type.

Because Oho tracks the expiry you configure, custom credentials feed the same compliance dashboards and notifications as verifiable ones, and can be required inside a screening package.