Skip to main content
Some clients want more than a shortlist to approve. A hiring manager who runs a weekly status call wants to know who is at interview, who was rejected, and who is new since last week. Emailing that table every Friday is work that gets stale on Monday. The portal can now show the pipeline itself: every candidate on the job, at their real stage, updated the moment you move them. You still decide which stages the client may look into, and which fields of a profile leave your workspace.

Two ways to share

Nothing changes for portals you already have. Every existing portal stays a hand-picked shortlist until you switch it.

Turn it on

1

Open the job's Portal tab

Every setting below lives in the What the client sees block on the job’s Portal tab. There is no separate page and no new menu.
2

Switch on live sharing

Turn on Share every candidate in the pipeline, live. A Pipeline stages list appears underneath, with every stage of this job ticked. Untick the stages the client must not look into. A candidate in an unticked stage is simply not in the portal, and comes back the moment you move them into an allowed stage.Use Find a stage to search a long pipeline, and Select all to reset.
3

Decide whether the client sees your stage names

Show pipeline stages off: the client sees each candidate with their own Yes, Maybe or No, exactly as today.Show pipeline stages on: the client sees the candidate’s current stage (Interview, Offer, Rejected, whatever your pipeline calls it) instead of their own verdict. Pick this when the client already knows your process and wants to follow it.
4

Choose the fields that leave your workspace

The checklist under What the client sees covers Photo, Name, Location, LinkedIn, CV file, Experience, Education, Languages, Current salary, Birthday and Criteria check. Turn off anything that should stay private.Education, Languages, Current salary and Birthday are off by default. A field you turn off is not merely hidden on the page: it is never sent to the portal at all.

What the client never sees

Your notes, conversations, tasks and internal files stay inside Yena in both modes. The portal only carries the fields you ticked, for the candidates in the stages you allowed. Anonymize Names, Allow Downloads and Allow Feedback work the same way as on a hand-picked shortlist.
One portal, one job. If a client has three open roles with you, give each role its own portal. Feedback and stage lists stay clean, and you can share a live pipeline on one role while keeping another one hand-picked.
Rejected is a stage like any other. Leave it ticked when the client wants to see who fell out; untick it when the client should only see people still in play.