πŸ₯‡ Issue Trainee certificates


In this article:

  1. How to create a certificate
  2. How certificates are issued
  3. What the trainee receives
  4. How to follow trainee progress
  5. How to edit, archive or delete a certificate
  6. FAQ


Certificates let you reward trainees with a digital certificate when they pass one or more scenarios in your workspace. A certificate is issued automatically, emailed to the trainee, and stays available on a public page that the trainee can print, share, or add to their LinkedIn profile. πŸŽ“
Each workspace manages its own certificates. You decide which scenarios earn a certificate, what it looks like, and whether your workspace issues certificates at all.


ℹ️ Certificates are not enabled by default. Contact your customer success manager to enable them for your workspace.



✍️ How to create a certificate

To create a certificate:

  • Navigate to Trainees β†’ Certificates in Warp Studio.
  • Create a new certificate.
  • Fill in the certificate details (see below).
  • Save the certificate.

Owner, Manager and Instructor roles of a workspace can create, edit and archive certificates.


πŸ“ Certificate details

A certificate consists of three parts:

  • Name - Shown on the certificate, for example "Safety Training 2026".
  • Scenarios - One or more published scenarios the trainee must pass to earn the certificate. You can select your own scenarios as well as scenarios shared with your workspace. Scenarios are selected individually; a course cannot be selected as a whole.
  • Branding - Choose how the certificate looks:
    • Workspace branding - Uses the logo and colours from your workspace settings, with your workspace name as the issuer.
    • Custom branding - Upload a logo, choose colours and enter an issuer name. The issuer name is what the certificate shows as the issuing organisation.

The texts on the certificate are fixed and translated automatically; they cannot be edited per certificate.


🎯 Passing threshold

The passing threshold is not part of the certificate. It is set by the scenario creator in the scenario's scoring settings (stars for completion).
This means that for a scenario shared with your workspace, you decide whether a certificate is issued for it, but you cannot change what counts as passing. A scenario with scoring disabled counts as passed once the trainee reaches an ending scene.
ℹ️ For more information on scoring, see βš™οΈ Scoring system.


πŸ… How certificates are issued

Certificates are issued automatically. After every finished attempt, Warp Studio checks whether the trainee has now passed all scenarios required for a certificate they don't have yet. If so, the certificate is issued.

  • Only passes from after a scenario was added count - Every scenario in a certificate has its own start date: the moment it was added to the certificate. A pass from before that date doesn't count. So if a certificate requires scenarios A and B, and the trainee passed A last month and B today, the certificate is only issued today if A was already part of the certificate last month. If it wasn't, the trainee has to pass A again.
  • Once per trainee - A trainee receives each certificate only once. An issued certificate is never updated afterwards, even if the trainee later achieves a higher score.
  • No retroactive issuing - Creating or editing a certificate never issues anything by itself. Only passing attempts made after you save the certificate count. A trainee who had already passed all required scenarios beforehand has to pass every one of them again; replaying a single scenario is not enough.
  • The play date counts, not the upload date - An attempt counts on the date the headset played it, not the date it reached Warp Studio. A scenario played offline before the certificate existed doesn't count, even if the headset uploads it afterwards.
  • Migrated certificates count from 22 October 2025 - If your certificate was migrated from before certificates had a per-scenario start date, there's no individual "added on" date to fall back on. For those certificates, every required scenario counts attempts from 22 October 2025 onwards β€” the date this start-date logic went live β€” regardless of when each scenario was originally added.
  • Excluded attempts - Test attempts and anonymised attempts never count towards a certificate.

πŸ’‘ Want trainees who already qualified to receive a new certificate? Ask them to replay all of the required scenarios, not just one.


πŸ“¬ What the trainee receives


Each issued certificate will be sent to the recipient's email and has its own page:

  • Public link - The page can be viewed without logging in, so the trainee can share it with an employer or auditor.
  • Language picker - The certificate can be viewed in English, Dutch, German, Spanish, Italian and French. It opens in the viewer's browser language by default.
  • Print - Uses the browser's print function.
  • Add to LinkedIn - Pre-fills a LinkedIn certification with the certificate name, issuer name, issue month and certificate link.

Each certificate reflects the moment it was issued: the scenarios, scores, completion dates, trainee name and branding at that time. Changing your workspace branding or editing the certificate later does not change certificates that were already issued.





πŸ“Š How to follow trainee progress

Open a certificate on the Certificates page to see its detail page. It contains two lists:

  • Issued - Trainees who have received the certificate, with the issue date, the certificate link and their stars per scenario.
  • In progress - Trainees who have played at least one of the required scenarios since it was added to the certificate, but haven't received the certificate yet. Per scenario you see whether it is completed or not completed, the stars, the last play and the completion date. Attempts from before a scenario was added to the certificate are not shown, so a trainee who passed it earlier appears as not played.




πŸ“€ Export

You can export a CSV of all trainees who received the certificate, including name, email, employee number, external ID, certificate link, issue date, and stars and completion date per scenario. The export is delivered by email.


✏️ How to edit, archive or delete a certificate

  • Edit - You can edit a certificate at any time. Changes only apply to certificates issued from then on; already issued certificates are not affected. Adding a scenario to an existing certificate starts that scenario's clock at the moment you add it, so earlier passes of that scenario don't count. Removing a scenario and adding it back later restarts its clock as well. Publishing a new version of a scenario doesn't restart anything: attempts on every version of the scenario count.
  • Archive - Stops issuing the certificate. Everything that was already issued is kept, and existing certificate links keep working.
  • Delete - Only possible as long as the certificate hasn't been issued to anyone yet. Otherwise, archive it instead.

⚠️ If a required scenario becomes unavailable, for example because your access to it expired or it was archived or deleted by its creator, the certificate shows a warning and can no longer be completed. Edit the certificate to update its scenarios.


πŸ™‹ FAQ

Do earlier passes count towards a certificate? Only if they happened after each scenario was added to that certificate (or after 22 October 2025 for migrated certificates, see above). A pass from before that date doesn't count and has to be repeated.
We already had trainees who'd passed everything required β€” will they get the certificate automatically once we set it up? No. Creating or editing a certificate never issues it retroactively. A trainee who had already passed every required scenario beforehand needs to pass all of them again after you save the certificate β€” replaying just one isn't enough.
A trainee says they never received their certificate email. What should I check? Open the certificate's detail page. If they're listed under Issued, you can share the certificate link with them directly β€” the email may simply have landed in spam. If they're listed under In progress, check the status per scenario: it shows what they still need to pass, keeping in mind that a pass from before the scenario was added to the certificate (or before 22 October 2025 for migrated certificates) doesn't count and has to be repeated.
A trainee passed a required scenario before it was added to the certificate β€” does that count? No. Every scenario in a certificate has its own start date: the moment it was added. A pass from before that date doesn't count, even if the trainee goes on to pass every other required scenario.
A trainee played a scenario offline and it only synced to Warp Studio later β€” does that count? It depends on when they played it, not when it synced. Warp Studio counts the play date, so a scenario played offline before the certificate (or that scenario) existed won't count, even though the upload happens afterwards.
Can I combine a few single-scenario certificates into one certificate that requires multiple scenarios? Yes, but combining them is a fresh start: editing a certificate to add scenarios means only passes from after that point count. Earlier passes on the separate certificates don't carry over automatically. Talk to your customer success manager before combining certificates, so you can decide together whether that trade-off works for your trainees.

Updated on: 23/09/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!