🚀 New Features
| Creative Editor for AIR Campaigns | Sites using AIR can now request to have the creative editor for individual campaign ads enabled in the backend. It makes editing each campaign creative quick and easy. |
| Resume Completeness Tracking in Analytics | Resume completeness can now be tracked. The completeness ranges are configurable, so resumes can be grouped in the way that suits your job board. This optional value can be added to your analytics on request. |
⏫ Improvements
| Feature an Organization Profile in Blog Posts | Blog posts have a new paragraph type that lets you select one organization profile to feature in the post. This makes it easy to showcase an employer directly in your editorial content. |
| Simple Export for Job XML Feeds | Site admins can now create XML job feeds through a new, simplified setup. Most technical settings are preset, so users only need to enter a name, choose any filters (occupation, upgrade, or organization), and set how often the export runs. The advanced export settings remain available for full control. |
✅ Bug Fixes
| Site Admins Can Access Recruiter API Keys Again | We fixed an issue where site admins got an "Access Denied" error on the recruiter API key page in the backend. Site admins can open the page and retrieve recruiter API keys again. |
| Imported Jobs Keep Their Own Logo | Imported jobs could show another company's logo when two jobs used image files with the exact same name, such as "logo.png". New importers now use the default option of renaming existing files, so each job keeps its own logo. |
| Multiple Locations in Featured Video Jobs Element | We fixed an issue where the "Featured video jobs" landing page element listed every location for jobs with multiple locations. It now shows the first location and places the others under the "+" icon, as on the rest of the site. |
| Correct Payment Entries on Orders With a Shared Stripe Account | When several frontends shared one Stripe account, a payment could also show up on another site's order. That order then displayed a duplicate or incorrect payment information in the backend. This only affected the entry in the backend, and no customer was charged twice. Order information is now only attributed to the frontend on which the payment was started. |
| Character Limit Now Applies to Each Skill | Saving a job with a very long skill could cause a generic error because the length limit wasn't enforced. Each skill field now accepts a maximum of 255 characters, so jobs save without errors. |