FAQ
Short answers to the questions we get most often.
Plans and features
- Do cheaper plans have fewer features?
- No. Every plan including Free has the full platform — designer, pathways, bulk issuance, reporting, sub-organizations, your logo and public page, and verification. Plans differ only in badges per year. API access, webhooks and SSO are the three Enterprise-only exceptions.
- What's the difference between a badge and an award?
- A badge is the template — design, criteria, skills. An award is one copy given to one person. Plan limits count awards per year; you can create unlimited badge templates on any plan.
- Is there a test environment?
- Not a separate one. Issue a badge to yourself — you'll get exactly what a recipient gets. Note that test awards count against your yearly limit (Enterprise has none), and archiving the badge afterwards doesn't refund them. The same goes for the API: there is no sandbox, and a test call issues a real award. Send
"notify": falseso the recipient is not emailed.
Badges and awards
- Can I edit a badge after issuing it?
- Its name, description, criteria and skills: only before the first award. After that they are locked, because they are part of a signed credential someone already holds; Duplicate the badge and edit the copy (see Managing badges). Its graphic can still be corrected by an organization admin, for example to fix a typo in the artwork: open the badge and choose Correct graphic. The corrected graphic replaces the old one on every award of the badge, including ones already sent, because a credential holds the picture's address and not the picture. Public badge pages show it at once; the picture in award emails already opened can take up to a day to change. Copies people have already downloaded, and images other sites such as LinkedIn have already copied, keep the old picture. A badge whose image file is shared with another badge (a duplicate) gets a new file instead, and credentials already issued for it keep the address of the old picture. The change is recorded in your audit log and the previous graphic is kept.
- What happens when I archive a badge?
- It can't be issued any more and leaves the default list, but every award already made stays live and verifiable. Archived badges have their own tab.
- Can I revoke an award, and can I undo that?
- Yes to both. A revoked award shows a Revoked banner and verification reports it as revoked. An admin can restore it if you change your mind. Both are on each row of the Recipients table. Enterprise accounts can do both through the API.
- Can I correct a recipient's name after issuing?
- Not by editing. A name cannot be changed once an award is issued. An admin revokes the award and issues a new one, and the old badge link then shows Revoked. Through the API, use a new
external_idfor the new award. - Does Incredify connect to a student information system?
- No. Recipients are entered by hand, uploaded as a CSV, or sent through the REST API on the Enterprise plan. A badge is not part of a transcript or academic record.
- Can I set an expiry date?
- Yes, optionally. In the dashboard, set Valid until when you issue, give a badge an Awards expire default in months, or add a
valid_untilcolumn to a bulk CSV; through the API, sendexpires_at. The award is valid through that day. After it, verification answers expired and the badge page says so. The date is signed into the credential, so it cannot be edited after issue: to renew, issue the badge again once it has expired, or revoke the award and issue again before then. No renewal reminders are sent and nothing renews automatically, so keep due dates in your own system and re-issue on your own cycle. - Can I record contact hours or credits, or print a certificate?
- There is no field for hours or credits: write them in the badge's description (for example "2.0 contact hours"). It is plain text, and Incredify makes no statement about whether any body accepts it. Incredify does not produce PDF certificates. A recipient can download the badge as a PNG or print the public badge page, which prints as a short record with the issuer, the date, their name if one was entered and, for a valid badge, the address where it can be checked, and anyone can verify the badge from its link. Do not put patient or health information in a badge, its description or its evidence: badge pages are public to anyone with the link.
- What evidence can I attach?
- Multiple items per award, each with a link and/or an uploaded file (PDF, PNG, JPEG, up to 4 MB) plus name, description, and narrative. Bulk CSV supports two link/text items per row and no files. See Issuing.
Recipients
- Do recipients need an account?
- Never. They claim, share, and download from a public page — no sign-up, nothing to install.
- How soon does a badge appear?
- Immediately. The claim page is live as soon as issuance is confirmed, and the email is sent right away; how fast it arrives depends on the recipient's mail system.
- Can I customize the claim page?
- It picks up your organization's name, and its verified-domain mark once that has been reviewed, automatically. Its layout and colours are Incredify's; per-badge layouts and custom domains aren't supported. See Branding and your public page for what carries your brand.
- Why can't I search recipients by partial email?
- Addresses are encrypted at rest, so partial matching isn't possible. Search the full address, or search by name (the search box says "Name, or full email address"). See Reporting.
Standards and data
- Which Open Badges version?
- Open Badges 3.0, as W3C Verifiable Credentials. Each award is an Ed25519-signed credential, and your issuer identity is anchored to your subdomain via
did:web. - What is did:web, in plain English?
- Your badges are signed with a private key that Incredify generates for your organization and keeps encrypted on its servers. The matching public key sits in a small public file that Incredify publishes at
incredify.net/issuers/<your-subdomain>/did.json. Anyone can fetch it and confirm that a badge was issued from your Incredify account and has not been altered. Checking a signature depends on incredify.net publishing that file. Full explanation in How verification works. - Can I export my data if I leave?
- Yes — CSV from Recipients, and a complete JSON export from
GET /api/v1/export. Credentials are standards-based files that work with any Open Badges 3.0 wallet, and recipients keep their claim URLs.
Your organization
- Can I have multiple admins?
- Yes. Invite colleagues under Settings → Members with the admin or issuer role. They don't need an account first; we email them an invitation, and they join when they sign in and accept it — see Settings, members, and roles.
- What is a sub-organization?
- A division inside your account — a school, department, or program — used to group badges and scope what each issuer can see. Each member belongs to one sub-organization, or none; you choose it as Access when you invite someone. See Sub-organizations.
- Can I change my subdomain?
- No. It's part of your cryptographic issuer identity, and every credential you've issued points at it. There's no rename path.
Related
Getting startedWhat Incredify does, and the shortest path from signing up to a badge in someone's hands.How verification worksWhy an Incredify badge can't be faked, in plain English — plus did:web, Open Badges 3.0, and the API.Plans and billingWhat each plan includes, how the annual limit is counted, and managing your subscription.
Still stuck?
Email us at hello@incredify.net — a human will answer.