Private build
Stronger account separation
Candidate, company, and operational records now have explicit per-user access boundaries throughout the marketplace data model.
What changed
Per-user isolation was enforced across hiring, watchlist, notification, entitlement, and profile data.
Marketplace tenant boundaries gained repeatable validation before release.
Why it matters
Private candidate proof and company workflows should never depend on an informal convention about which account can see a record.
Find it in Quiet Search
The protection is applied behind the Hiring, Trust, and account-specific marketplace surfaces.