Updating an issued credential

If you spot an error in a credential after issuing it (a misspelled name, an incorrect date, a dynamic field with the wrong data), you can correct it without having to revoke it and reissue it from scratch. What happens when you correct it depends on whether the earner has already accepted it or not.

If the credential is pending (the earner hasn’t accepted it yet)

The platform updates the credential on the same record — no new credential or new version is created. The earner still sees the same acceptance link, now with the corrected data.

1. Go to Digital credentials → Issued credentials.
2. Find the credential with Pending status (or In review — see Earner correction suggestions).
3. Click the update icon on that row (the circular arrows one). It takes you straight to the issuance form, with a notice at the top: “In-place update. Changes will apply without versioning the credential.”

4. Correct the field or fields you need.
5. Save your changes. If you need the correction to go out without an email notification, see Silent issuance.

You can correct virtually any field from the original form (including attached evidence), except the email address — that can’t be changed once the credential has been issued; if the email is wrong, you’ll need to revoke it and issue a new one.

If the credential has already been accepted (or has expired)

Here the platform doesn’t modify the original — for safety, a credential the earner has already accepted (or that has already expired — see Managing credentials) can’t be altered directly (it could change something the person already shared or downloaded, or affect the record of when it expired). Instead:

1. When you save your correction, the platform creates a new credential with the corrected information (V2, V3…, depending on how many times it’s been corrected).
2. If the original credential was Accepted, it gets marked with Versioned status — see the status table in Managing credentials. If it was Expired, that credential’s original link shows a notice to switch to the new version.
3. The earner receives the new version to accept, following the same flow as a normal issuance.

⚠️ Important: if you have digital signing enabled and the original credential was already signed, check with your technical team whether the new version needs a new signature — regenerating the PDF doesn’t always reapply the signature automatically.

If you try to edit right as the earner is accepting

There’s a safeguard to prevent you from editing a credential at the same moment the earner is accepting it. If this happens, the platform lets you know the status changed while you had the form open and asks you to try again — check the credential’s current status before retrying, because if it’s already been accepted, your correction will follow the new version flow instead of the direct-edit one.

Edit history

Every credential keeps an audit trail with all the updates it’s had: approved corrections, rejected ones, and direct edits — with the date and the name of the administrator who made the change, and the detail of which field changed (before → after).