This update is about how Navigatr looks from the outside, and what your badges carry on the inside. The public side of Navigatr has been rebuilt and now sits alongside the product itself, and your badges travel with more of the detail that proves them.
Key features
Everything about Navigatr, in one place
The public side of Navigatr has had a thorough revamp: pages written for individuals, pages for organisations working out whether Navigatr is for them, pricing set out plainly, an introduction to the team, and a straightforward way to get in touch.
The bigger change is where it lives. Until now, all of this sat on a site of its own, separate from the product. It now sits at the same address as the platform, so reading about pricing and using Navigatr are no longer two different places.
If you are signed in, the navigation comes with you. Following a link to the pricing page or the team page keeps you inside Navigatr, with the same header and the same look, rather than dropping you onto something that feels like a different product.
How to access: use the links in the header or footer, or go to navigatr.app.
Badges that carry more with them
A digital badge is only as useful as the data inside it. Your badges now carry more of that data in the Open Badges 3.0 format, which is what other systems read when someone shares a badge outside Navigatr.
Badges now include the evidence attached to them and a description of what the recipient actually did, alongside the type of achievement and the language it was delivered in. The issuer identity resolves properly too, so anyone checking a badge can confirm who issued it.
Endorsements that arrive as signed credentials from another platform now import too, where before they were quietly skipped. We keep an endorsement only when the signature covering the badge covers the endorsement as well, so what you see on a badge is what its issuer actually signed.
There is nothing to switch on, and this is not limited to new badges. Any badge you have issued through Navigatr carries the extra detail when it is downloaded as an Open Badge 3.0 credential.
How to access: see Downloading Your Open Badge and Endorsing a Digital Badge.
Changes
On a pathway Job Feed, the Job Titles filter now searches two Lightcast job taxonomies at once, so one search finds both broad occupations and specific job titles. Results are wider and ordered so the closest matches come first. See Enabling the Job Feed on Your Pathway.
Email addresses are no longer accepted in names that show publicly, including your profile name, an issuer name, and a badge recipient name. If you have been using an email address as a name, you will be asked to change it.
The email people receive when they claim a badge now matches the others. It carries a plain-text share link, and the links inside it point where they should.
On a badge you have earned, Share is now a clearly labelled main button rather than an icon on its own.
Bug fixes
Downloads from the bulk issuing error table are now escaped correctly, so a spreadsheet cannot treat a value in them as a formula.
Approving a badge change request now validates the details it is about to apply, so you are told which field needs attention instead of seeing a technical error.
Signing in now takes you straight to your dashboard rather than to the public home page.
You can record 0 years of experience in your settings.
Activities without a date now show their icon.
Several colours that clashed in dark mode have been corrected.
A provider name shown in the Issued By column, and an endorsement description on a badge card, are now escaped properly.
API and integrations
Removed: the endpoints that returned matching jobs for a badge and for an activity have been retired, along with the columns behind them. Job feeds on pathways are unaffected. If you call either endpoint, you will need to stop.
Evidence sent to the API is now validated and size-bounded on every write path, so a malformed or oversized evidence entry is rejected at the door rather than stored.
Endorsements are accepted only when the proof attached actually covers the endorsement.
Allowed origins now match whether or not you send a trailing slash.
What this means for you
Learners: Your badges now carry more detail about what you did and who issued it, which makes them easier for an employer or another platform to check. Sharing a badge is a little clearer too.
Providers: There are refreshed pages to point people at when you are explaining Navigatr, with pricing written plainly. If you run a Job Feed on a pathway, searching for roles should now find what you are looking for in one go.
Community admins: The same applies across your providers. The refreshed pages give you something to share with partners and funders.
API users: Two job endpoints have been retired and evidence validation is stricter. Please read the API and integrations section above before your next release.
Need help? If you have any questions about the refreshed pages, your badge data, or the API changes, the easiest way to reach us is through the in-app messenger inside Navigatr. You can also email us at [email protected].