The words this product uses
Design, programme, credential, recipient — and why the distinctions matter.
| Word | What it means | What it is not |
|---|---|---|
| Design | Artwork plus field positions. The thing that gets drawn. | Not the programme. One design can serve several. |
| Credential group | The programme: what a credential is for. Holds the designs, the expiry policy, the ID format. | Not a template. |
| Credential | One issued thing, to one person, with its own ID and public record. | |
| Recipient | A person, as an entity, across every credential they hold from you. | Not an account. They never log in. |
| Signatory | A name, a title and a signature image. |
Why "recipient" is not "account"
A recipient is a real entity in the data — that is what makes the billing meter, the engagement figures and the hours ledger possible at all. But there is no recipient login, and there is not going to be one. A credential is checked from its public page by whoever is holding it; asking the person it is about to create an account to prove something about themselves gets the relationship backwards.
Why the design and the programme are separate
They were one thing in an earlier version of this product, and splitting them was most of the work of the second. With them joined, awarding a certificate and a badge for the same course meant two programmes, two ID sequences and two sets of settings — and the badge ended up with a different expiry policy from the certificate by accident.