🚀 New Features
| Credly Certification Badges on Applicants' Profiles | Applicants can now connect their Credly account to automatically import and showcase earned certification badges directly on their profile (CV), making it easier for recruiters to spot relevant credentials at a glance. Each badge displays with an icon, name, and description, and can be reordered or removed at any time. Note: This feature requires the job board to have an active Credly issuer account. |
| Authorize.Net Now Supported for Payment Processing | Authorize.Net can now be configured as the payment provider alongside Stripe, supporting a wide range of card processors including Visa, Mastercard, Apple Pay, Google Pay, PayPal, and more. This adds more flexibility in how payments are handled, while recruiters experience the same familiar checkout flow. |
| Single Sign-On Support for Recruiters | Recruiters can now sign in using their existing company credentials via Okta, a third-party Identity and Access Management (IAM) platform. When Okta is enabled, authentication is handled entirely by Okta — removing the need for a separate job board username and password. |
⏫ Improvements
| Improved Salary Range Display on Job Listings | Job listings using the free input salary range option now adapt dynamically to the salary input. When minimum and maximum values are equal, a single value is shown. When only a minimum is set, the listing displays "From"; and when only a maximum is set, it displays "Up to" — replacing the previous behavior of showing 0. The Google for Jobs schema has been updated to reflect all of these changes. |
| Support for Keycloak Single Sign-On for Applicants | We have expanded Single Sign-On (SSO) support for applicants by integrating additional identity providers. This enhancement enables organizations to offer candidates a wider selection of login options, reducing registration friction and simplifying the onboarding flow for candidates. |
✅ Bug Fixes
| Organizational Logos Now Display Correctly | When importing jobs from XML feeds, logos with identical filenames from different sources were all resolving to the first file encountered, causing subsequent jobs to display the wrong logo. Duplicate filenames are now renamed automatically, ensuring each job always references the correct logo. |