> ## Documentation Index
> Fetch the complete documentation index at: https://support.yena.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Portal projects: one link per client

> A portal workspace can carry every search you run for a client — one URL, project-specific feedback, batch by batch.

The portal is per client, not per job. That distinction does quiet work for you.

## One workspace, many projects

When a second mandate starts for the same client, attach it to their existing portal workspace as a new **project** instead of minting a new link. The client keeps one URL for everything you run for them; feedback stays project-specific.

## Batches

Candidates are presented in **batches** — the client sees "Batch 1", "Batch 2" per project, with the summary counting to-review, approved, and declined across the portal. Presenting in deliberate batches beats trickling candidates one at a time: it frames the review as a sitting, not a drip.

## Why this matters commercially

The portal link becomes a fixture in the client's workflow: the place where hiring with you happens. By the third mandate, sending "it's in the portal" is the entire status update — and the [careers-page links](/en/portal/public-links) hanging off the same workspace mean their inbound flows through you too.

<Note>
  Project naming is client-facing — "Servicetechniker Frankfurt" reads better than an internal reference number. You set it when creating the portal workspace.
</Note>