What's new

Release 4.2 reached all tenants overnight. Highlights:

Request quality checks. When a request is raised, it is now checked for the fields matching depends on - ontology skills, a real start date, commitment level. Incomplete requests can still be saved, but they are flagged in the queue and the requester sees exactly what is missing. Early tenants saw first-time-complete requests rise noticeably within a month, which means less clarification work at triage.

Bench alerts. The utilisation dashboard can now send an alert when the bench in a grade or skill cluster crosses a threshold you set, so the weekly meeting hears about build-up before it is three weeks old.

Also in 4.2. Match breakdown panels can be attached to a request as a snapshot when sharing a shortlist; the triage note field supports templates; and role-mapping changes now take effect on next sign-in rather than overnight.

No admin action is required. Full notes in the admin release channel.

The legacy CSV export - the “Export (legacy)” button on list views and the /export/v1 endpoints behind it - will be retired on 30 September 2026. It predates the current permission model and cannot respect row-level scopes, which is why it is going.

What replaces it. Two options, both already available:

• Scheduled exports in the reporting section: pick a view, a format and a cadence, and receive the file by email or SFTP. Right for most teams currently downloading CSVs by hand.
• The reporting API (/api/v2/reports): for anything automated. Same data, JSON or CSV, and it respects the caller’s scopes.

Dates. From 1 August the legacy button shows a retirement warning. From 30 September both the button and the endpoints return errors.

Who is affected. Tenant admins have been emailed a list of accounts and integrations that used the legacy endpoints in the last 90 days. If your team maintains a spreadsheet that starts with a legacy CSV download, now is the time to switch it to a scheduled export - it is a ten-minute change, and the learning team can help if the old file’s columns need mapping.

Workday connector v2 is available to all tenants from today. The change that matters: worker record changes (joiners, movers, leavers, grade and location updates) now sync on change rather than in a nightly batch. Typical lag drops from up to 24 hours to a few minutes, with the nightly run retained as a reconciliation sweep.

Also in v2:

• Absence and leave data now included, feeding availability directly.
• Certification sync from Workday’s credentials domain.
• Per-record error reporting in the sync log, replacing the all-or-nothing batch status.

Action required from platform admins. v2 needs one additional permission on the Workday integration user (Get access to the absence domain) and a re-authentication in Admin → Integrations → Workday. Existing v1 connections keep working unchanged until the v1 retirement, planned for early 2027 with formal notice to follow. The Workday integration doc has been updated for v2.

The new utilisation dashboard begins rolling out to tenants this week, with all tenants live by 29 May. It replaces the legacy utilisation report, which remains available until August.

The headline change is direction: the old report looked backwards at the last four weeks, while the new dashboard leads with a six-week forward view. Booked and pencilled work are shown separately, so you can see where capacity problems are forming while there is still time to act on them.

Other changes:

• Heatmaps by grade, practice area and skill cluster, with drill-through to the individuals behind any cell.
• Bench view that distinguishes people rolling off engagements this week from people unassigned for longer.
• Scheduled email snapshots for people who want the picture without logging in.

Access follows existing reporting permissions - if you could see the old report, you can see the new dashboard. The Reading utilisation signals course on this portal has been written around the new dashboard and is the recommended starting point.

This portal replaces the collection of PDFs and recorded webinars that previously served as ProFinda training. Everything has been rewritten for how teams actually use the platform.

What is here now:

• Pathways - ordered sequences of short courses by role, starting with Resourcing fundamentals for new resourcing leads and coordinators.
• Docs - reference pages for concepts, integrations and administration, written to be read in under five minutes.
• Videos - short walkthroughs of common tasks, none longer than seven minutes.
• News - release notes and platform announcements, in one place, in plain language.

If you are onboarding a new team member, point them at the Your first week doc and the Resourcing fundamentals pathway; that pairing covers the first month. Feedback and requests for topics go to the learning team via the link in the footer.

Release 4.1 is live on all tenants as of this morning. Two changes you will notice.

Near-match ranking. Candidates surfaced through ontology expansion (related skills rather than exact ones) previously clustered too close to exact matches in some searches. The distance penalty is now calibrated per relationship type, so exact-skill candidates reliably rank above near matches with otherwise similar profiles. Expect fewer surprises in the top five of a shortlist.

Search performance. Median search response on tenants above 5,000 profiles has dropped from 3.1 seconds to 1.4. No action needed.

Smaller items. The request form now warns when a skill was entered as free text rather than selected from the ontology; the match breakdown panel shows evidence dates without hovering; and CSV imports of historical engagements accept the ISO date format alongside the existing ones.

Full technical notes are in the admin release channel.