https://www.loom.com/share/4b4dd2d3ddc043df8936c726a98bde16
Most searches don’t need to be hidden. But sometimes you’re working on something sensitive — an internal hire or a client engagement under NDA. Confidential searches lock down the search and everything attached to it (notes, assessments, comp, tasks, calendar events) so only the people working on it and admins can see it. Everyone else can still find the candidates in the rest of the database; they just can’t tell the search exists.
Once confirmed, a 🔒 lock icon appears on the search. That’s your visual cue the search is now confidential.
<aside> 💡
Only admins and team members with edit access on the search can toggle confidentiality. If you don’t see the option in Actions, you’re not on the search team.
</aside>
When a search is marked confidential, visibility splits into three groups:
| Role | What they see |
|---|---|
| Admins | Everything — the search, its candidates, notes, assessments, comp, tasks, calendar events |
| Team members on the search | Everything (same as admins for this search) |
| Everyone else on the team | Cannot see the search exists. Cannot see any notes, assessments, comp, tasks, or calendar events tied to the search. Can still see the candidate’s profile and the rest of the database. |
The important subtlety: candidates inside a confidential search are not removed from search results for other teammates. People searching the database will still find Yen Zhang (or whoever) — they just won’t see the confidential association, and they won’t see any of the confidential notes, comp, or assessments your team has added against this specific search.
This is intentional. Confidentiality is about hiding the engagement, not the person. The rest of the database stays searchable.