Skip to content

Managing badges and awards

Editing, duplicating, archiving, filing into folders, revoking, resending, and moving badges between sub-organizations.

Editing a badge

A badge can only be edited before it has been awarded

Once even one person holds it, its name, description, criteria and skills are locked. They are part of a signed credential already in someone's hands, and the public badge page shows the signed wording. To change them, duplicate the badge and edit the copy. You can still archive the badge or move it to a folder, change its Awards expire default (it only affects awards issued afterwards), and an admin can still correct its graphic. Usually badge pages for awards already made then show the new graphic; if the image file is shared with another badge (a duplicate, for example) or cannot be replaced in place, awards already made keep the old graphic and only new awards use the new one. The change is recorded in the activity log.

Duplicating

Duplicate on the badge detail page copies the design and details into a new, unissued badge. This is the standard way to run a new cohort with tweaked criteria, or to spin a variant off a house template.

Archiving

Archiving retires a badge from circulation. Archived badges can't be issued and drop out of the default badge list, but every credential already awarded stays live and verifiable. Nothing a recipient holds is affected.

Folders

Folders are a way to file your badges so the badge list is easier to scan. They are for your team only: recipients never see them, they don't appear on badge pages or in the credential, and they don't change who can see or issue a badge (sub-organizations do that).

  • Who can create them. Organization admins create, rename and delete folders, from the chips above the badge list on the Badges page. Names can be up to 60 characters, and two folders can't share a name (capitals don't count). An organization can have up to 100 folders.
  • Who can file badges. Anyone who can edit a badge can file it: use Move to folder on the badge's card, or on the badge page. An issuer assigned to a sub-organization can file only that sub-organization's badges. A badge is in one folder or none.
  • Finding badges. Choose a folder chip to see only its badges, or Unfiled for badges in no folder. The choice is kept in the page address, so you can bookmark it, and it works together with Active, Drafts and Archived. The numbers on the chips count only the badges you can see.
  • Deleting a folder never deletes badges. Its badges simply become unfiled.

Revoking an award

Revoking applies to one person's award, not the badge. Use it when a credential was issued in error or has been withdrawn. Revoke is on every row of the Issued table on the badge page and of the Recipients table. You are asked to confirm, and can add a reason. Issuers see the button too, but only admins can use it: an issuer who tries is told so. To withdraw many at once, an admin ticks the boxes beside active awards on Recipients (the box in the header selects every active award on the page), optionally adds a reason, and chooses Revoke selected. You are asked to confirm with the count, large selections are processed in batches of 50 with progress shown, and awards that were already revoked are skipped and reported.

  • The claim page stays reachable but displays a clear Revoked banner with the date.
  • Verification actively reports the credential as revoked — this is the point of revoking rather than deleting.
  • You can record a reason. It is kept for your organization's records (it appears in the recipients export, which admins and issuers can download, and in the API) and is not shown on the badge page or returned by the public verification check. Restoring the award clears the reason: the activity log keeps who revoked and restored it and when, but not the reason, so export the recipients list first if you need it. Before 12 November 2026 the verification check did return it to anyone with the badge link.
  • Revoking frees the recipient to be issued that badge again later, which is how recertification is handled. The earlier award's page keeps showing Revoked.

Revoking is reversible

An admin can restore a revoked award with Restore on the same row (it asks "Verify as valid again?"), putting it straight back to active. If the person has since been issued the same badge again, restoring is refused until that award is revoked. So revoking a credential you're unsure about is a safe, recoverable move rather than a one-way door.

Note that revocation doesn't break the signature — the credential is still authentically yours. What changes is the status that verification reports, which is exactly what you want: a withdrawn credential should be provably withdrawn, not merely missing.

Resending a claim link

Resend appears on both the badge detail page and Recipients. It re-sends the original badge email to the same address. Use it when a recipient never got the first one, or lost it. Revoked awards can't be resent. Each award's email can be resent up to 3 times in any 24 hours, and an organization can resend up to 100 in 24 hours.

Moving and copying between sub-organizations

Admins can move a badge to a different sub-organization, or copy it into one, from the sub-organization panel on the badge detail page. Moving changes which issuers can see and award it; copying leaves the original in place. Both are organization-admin actions, done in your own dashboard.

Related

Still stuck?

Email us at hello@incredify.net — a human will answer.