The credential lifecycle, start to signed.
Seven steps from evidence submitted in your platform to a portable, verifiable credential the learner owns. No new tools for learners to adopt — the work stays inside your community.
Meet learners where they are
Connect it to where your community already meets — Circle, Notion, Thinkific, or wherever your programs run. You define the credential and the conditions that earn it — modules completed, discussion contributed, prerequisite badges held.
Learner submits evidence
The learner completes the submission without leaving the community. RecWorks collects only what's needed to issue and deliver the credential — name and email.
Review — or auto-issue
A reviewer evaluates the evidence against your criteria, or issuance runs automatically for participation-based recognition. Multi-condition logic is evaluated before anything is signed. For organizations with scoped reviewers, submissions route by tag — read from your platform's API where it's exposed (Circle, today), or from an uploaded roster.
Signed OBI 3.0 credential
The credential is issued as an Open Badges 3.0 / W3C Verifiable Credential, cryptographically signed with decentralized issuer identity (did:web) anchored to your own domain.
Delivered by email
The learner receives the credential directly. It's theirs to keep — portable, and independent of any single platform or vendor.
Publicly verifiable page
Every credential has a public verification page anyone can check against the cryptographic signature and your issuer identity — no login, no learner account, nothing to install. The signed credential itself is portable and belongs to the learner.
Shareable to LinkedIn
The learner shares the credential to LinkedIn and beyond, with the verification link intact. Recognition travels with the person, wherever their work takes them next.
Want to see it in your community?
We'll walk through setting up a credential in your actual platform.