Product updates.

Public Profile visibility on Privacy & security

Privacy & security now holds Public Profile visibility: Public profile, Show contact links, and Include in search. Contact links stay off until you opt in, and Include in search adds an opted-in Public Profile to Public Discovery Search and search-engine indexing. Child settings stay saved while the profile is private.

Open Privacy & security

Auto-publish and Directory listing on Issuer organizations

Issuer organizations settings now groups each Organization with its Workspace access, and adds Auto-publish and Directory listing. Auto-publish marks future credentials from that Organization public on your Public Profile. Directory listing is how you appear on that issuer’s public Recipients page after you have a credential in your Wallet.

Open Issuer organizations

Post a verified credential to LinkedIn

Connect LinkedIn from Connected apps as a Destination. On a verified issued credential, Share now includes Post to LinkedIn: confirm a fixed preview, then OpenCredia posts the title, issuer, and Public Credential Page URL. Add to LinkedIn is unchanged.

Open Connected apps

Import a signed Open Badge into your Wallet

Import a signed Open Badges 3.0 credential into your Wallet from a baked image, URL, or JSON. OpenCredia verifies it first and rejects Open Badges 2.0 files. If the subject is not a verified email on your account, add that address under Account first.

Import a credential

Dashboard adds Overview, Discover, and credential views

Your Dashboard now has Overview for wallet activity and Discover for achievements and skills based on your Wallet. Activity snapshot counts Views when people open your public credentials, alongside Credentials, External credentials, and Shares.

Open your Dashboard

Owners can register SSO from Organization settings

Organization owners can register an SSO identity provider from Organization settings. Sign in with SSO still needs a verified domain DNS record before it goes live.

Sign-in explains when human verification cannot load

If human verification cannot load on sign-in — for example on a blocked network — the form now explains what happened and lets you retry. You can still email a sign-in link. Password, Google, Microsoft, and SSO stay unavailable until verification loads.

Verified emails confirm only while you are signed in

Adding a verified email now asks you to confirm while signed in. Opening the mail link alone no longer attaches the address to your account.

Invites no longer skip authenticator sign-in

Accepting an organization invitation still grants membership. If your account already uses an authenticator app, you sign in with that factor instead of being signed in from the invite link.

Wallet connections ask before they get access

Hosted Open Badges wallets now ask you to allow or deny access before OpenCredia issues an authorization code. Visiting the authorize link while signed in no longer grants access by itself.

Sign-in remembers the last method you used

Sign-in remembers the last method you used on this browser — email, an email link, Google, Microsoft, or SSO — and marks it on the next visit so you can get in faster.

Organizations can prove DNS control of their website

Organization administrators can add a DNS TXT record for the website URL on Organization Details. After OpenCredia finds the record, Public Credential Pages, issuer profiles, and the Verifier can show that OpenCredia verified DNS control of that domain. The check is DNS control only; it is not legal-identity review.

Owners choose what SSO sign-in can grant

Organization owners can choose whether Sign in with SSO adds a Viewer on the Main workspace or only honors a pending invitation. Sign-in still creates or links an Account either way. The Activity log records when SSO adds that Viewer access.

Admins can correct or clear recipient contact data

Workspace admins can correct or clear Recipient contact fields from the recipient page, which changes later delivery and claim invitations only and leaves issued credential snapshots unchanged. Unused claim invitations expire when an email is cleared or changed. The Activity log records which fields changed and why, not the contact values.

Keyboard and announced-error fixes on claim, verify, and sign-in

Skip-to-content now lands in a focusable main region on claim, sign-in, public credential, verifier, and issuance pages. Claim email-mismatch errors are announced, claim card titles are headings, and the navigation progress bar respects prefers-reduced-motion. These are accessibility fixes, not a WCAG certification.

Activity logs can be filtered and exported

Organization owners and admins can filter Activity logs by event type and date, then download a CSV of that same filtered view. Exports keep the newest 10,000 rows and write an Activity log entry for the download.

Issuer chip now states what it checks

The issuer chip on Public Credential Pages, Wallet, Public Profiles, Collections, and the Verifier now reads Issuer on OpenCredia. It means the issuer's profile and signing key are hosted here. OpenCredia has not verified the organization's legal identity.

Cloudflare is listed as a Subprocessor

The published Subprocessors page now includes Cloudflare. Organizations that use that list for Data Processing Agreement review should treat it as the current vendor exhibit.

View Subprocessors

Public credentials expose less personal data

New credentials hide readable recipient and Organization identifiers behind an opaque subject id and hashes. Public Credential Page and Verifier URLs are no longer offered to search engines.

Webhook signing secrets are encrypted at rest

Webhook signing secrets are encrypted at rest. Creating or rotating a subscription still shows the HMAC secret once; later views keep only a prefix.

Organization owners can rotate signing keys

Organization owners can rotate the Signing Key from Issuer settings. New issuances use the new key; previous keys stay in the public JWKS so existing credentials still verify.

How keys work

Password changes sign out other devices

Changing your password now signs out every other signed-in device. Deactivated accounts can no longer keep using an open session.

Verifier results match a real check

Paste Credential JSON-LD downloaded from a Public Credential Page and the Verifier now checks the real signed credential: an unchanged download verifies, a changed body fails. Results show overall status, a live checked-at time, the recipient, and human comments on How we checked.

Open the Verifier

Verifier form and one-time results

The public Verifier is now its own tool: check a Credential URL, Credential JSON-LD, or VC-JWT, then see a one-time Verification result. Nothing you paste is stored. Check another credential starts an empty form; reloading the result returns you to the form.

Open the Verifier

Give a Pathway its own image

Pathways can now have their own square image, using the same size rules as a Badge Template image — not a wide Issuer Collection cover. Issuers upload it on the pathway form. Public pathway cards, related-pathway cards, and progress cards show it.

Browse Senda Pathways

Attach a Pathway from a Badge Template

Issuers can attach a Badge Template to Pathways from the template form, the same way Issuer Collections already work. A Pathway still uses existing credentials — it does not get a separate badge type. If a credential appears in a public Pathway, the Public Achievement Page and the Public Credential Page show that Pathway below the credential content, and pathway cards say how many credentials you earn.

Browse Senda Pathways

See your progress along a Pathway

Pathways now show how far you have come from the credentials you already hold — there is nothing to enroll in. A Public Achievement Page names every public Pathway a credential is a step on; signed-in Pathway pages mark earned and expired steps and point to the next required one. Your Wallet adds Continue your pathway, your Public Profile shows progress from published credentials only, and issuers can filter Analytics and exports by Pathway.

Browse Senda Pathways

Issuer Collections and Pathways on Issuer Profiles

Issuer Profiles now publish Issuer Collections and Pathways, which issuers manage in the Issuer console. An Issuer Collection groups Badge Templates thematically; a Pathway orders them toward a named outcome. Public indexes add sort and search, issuers can filter Analytics by either grouping, and View a live example opens the Senda Academy demo.

Browse Senda Collections

Public Profile credential cards

Public Profiles now show Featured and Public credentials as cards. Larger profiles can search by name or issuer and sort by Default, Most recent, or Name. Featured stays on the first page and is not filtered by search.

View Sofia Reyes

Searchable Recipients on Issuer Profiles

Issuer Profile Recipients is now a searchable, sortable browse. Each card shows name (linked to a Public Profile when available), optional title and location, skills from earned Badge Templates, credential count, and last earned.

Browse Senda Recipients

Public Earned credentials, Recipients, and Senda showcase

Issuer Profiles now include public Earned credentials and Recipients pages. Earned credentials are credentials the Organization earned as subject; Recipients are individuals this issuer credentialed. Senda Academy is a Public showcase Organization for the demo — it is not a Verified Issuer.

View Senda showcase

Sign in with Microsoft for existing accounts

Existing accounts can sign in with Microsoft when the Microsoft email matches the account email or a verified email on that account. Sign in with Microsoft does not create accounts and is distinct from Sign in with SSO.

Sign in with SSO for the Issuer console

Issuer console operators can sign in with an Organization-linked identity provider. Sign in with SSO is distinct from Sign in with Google and is not offered on Wallet sign-in.

Sign in with Google for existing accounts

Existing accounts can sign in with Google when the Google email matches the account email or a verified email on that account. Sign in with Google does not create accounts.

Public security and privacy pages

Public security and privacy pages spell out how OpenCredia handles accounts, issuer data, and credentials — without claiming certifications we do not hold.

Read security practices

Verification Checklist and How we checked

The Public Credential Page now shows a Verification Checklist of narrative issuance facts. How we checked lists the Technical Checks behind that checklist.

Dedicated Public Achievement Page

Public Badge Templates now have a dedicated Public Achievement Page. The issuer appears as a name link, and the catalog stays on the Issuer Profile.

Wallet import, collections, and Public Profile

Earners can import External Credentials into the Wallet, organize Collections with covers, and show expanded Public Profile fields when the profile is public.