> ## 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.

# Custom stages and pipeline templates

> Reshape a single job's pipeline, or set workspace templates so every new mandate starts with your process.

The default pipeline (New → Applied → Screening → Longlist → Shortlist → Interview → 2nd Interview → Offer → Hired, plus Postponed and Rejected) fits most desks. When it doesn't, two levels of control:

## Per job: rename and add stages

Every column's **⋯ menu** on a job's pipeline offers **Rename** and **Add Stage**. An executive search might want "Referenzen" between 2nd Interview and Offer; a temp desk might collapse the interview stages entirely. Changes apply to that job.

<Frame caption="The column menu: rename or add stages per job">
  <img src="https://mintcdn.com/yena/_yA7y7-DV4HpWgMr/images/screenshots/pipeline-stages.png?fit=max&auto=format&n=_yA7y7-DV4HpWgMr&q=85&s=d127abf747fcdaa67a3067299bd905be" alt="Pipeline with column menu options" width="1770" height="823" data-path="images/screenshots/pipeline-stages.png" />
</Frame>

## Workspace-wide: pipeline templates

<Frame caption="Workspace pipeline templates in Tenant Admin">
  <img src="https://mintcdn.com/yena/Km6uj7EB8i_TCgxz/images/screenshots/pipelines-templates.png?fit=max&auto=format&n=Km6uj7EB8i_TCgxz&q=85&s=d54dd5363c45518077990a2076865e83" alt="Pipeline templates" width="1920" height="855" data-path="images/screenshots/pipelines-templates.png" />
</Frame>

**Tenant Admin → Pipelines** holds the workspace templates, so every new mandate starts with your process instead of the default. Set it once when your team agrees on a flow; per-job edits still work on top.

## Why stage hygiene pays

The [Pipeline Funnel in Reports](/en/workspace/reports) aggregates by stage across all jobs. Consistent stage names are what make "where do our searches stall?" answerable — the funnel is only as honest as the columns.