Certificate upgrades: permissions, templates and regeneration
Certificates are proof. Proof that someone's food safety training is current, that a contractor holds the ticket they said they did, that your team is compliant when an auditor asks. Getting them into SuperPath, and getting them looking right, shouldn't be the fiddly part.
This release makes certificates easier to manage for admins and easier to keep current for everyone else. You can now decide who's allowed to add them, attach a certificate to learning as you build it, pull real details onto a custom design, and regenerate a certificate whenever something changes.

Decide who can add certificates
Until now, only admins could manually add a certificate to someone's profile. That works fine for smaller teams, but it puts a bottleneck in front of every external ticket, licence and accreditation your people already hold.
You can now choose from three levels:
- Everyone. Staff and contractors upload their own certificates. Ideal in heavily regulated environments where people hold qualifications earned outside your platform.
- Managers and admins. Managers take responsibility for their own team's records, without opening it up account wide.
- Admins only. The existing behaviour, if you'd rather keep it tightly held.
Worth knowing: giving people the ability to add a certificate doesn't let them create one. They choose from the certificates your admins have already set up, so your library stays clean and your branding stays intact.
Attach a certificate to learning while you're creating it
This one came straight from customer feedback. Previously you had to create the certificate, then go into the pathway or course separately to attach it. Two jobs, two places, easy to forget the second one.
Now you can search for your content from within the certificate itself and attach it there. Build the certificate, connect it to the course or pathway it belongs to, done. When a learner completes that learning, the certificate is awarded automatically.

Build one custom certificate and reuse it everywhere
If you've been designing a separate certificate for every course, this will save you a lot of time. Custom certificates can now pull in details at the moment they're awarded:
- Certificate title: so one blank branded template covers dozens of courses instead of one.
- Date awarded: which is what most auditors reach for first.
- Score: where the learning actually produces one (a SCORM course, or a course built in our course builder). If your pass mark is 80% and someone scored 92%, you can show it. It's optional, so leave it off where it isn't relevant.
The practical upshot: create a template with your branding and an empty middle section, and let SuperPath fill in the rest. There's a downloadable starter template if you'd like a head start.
You can also preview before you commit. Enter some example details, hit Generate preview, and you'll get a PDF to check your layout and spacing properly rather than guessing.

Regenerate a certificate when things change
Change your certificate design and the PDFs already sitting on people's profiles don't magically catch up. Now you can head to a user's profile, open their certificates, and hit Regenerate. A fresh version of the PDF is attached in place of the old one.
Handy when you've rebranded, fixed a typo, or updated a template after certificates have already gone out.

What this means day to day
Fewer admin requests landing in your inbox, because managers and staff can maintain their own records. Fewer templates to build, because one custom certificate now serves many courses. And no need to reissue anything by hand when a design changes.
Certificates are already switched on if you're using them. The new permission setting lives under Settings, Features, and the rest is waiting for you in Manage Certificates. Worth five minutes to have a look.





































