If you run the same recruitment every quarter, or look for five people for the same role in five cities, do not rebuild the process from scratch. Duplicate a project that already works.
Where it is
On the project list, in the action column on the right of the row. The icon's tooltip says Duplicate project. The button is not inside the project itself — duplicating happens from the list.
The action icons appear when you hover over the row.
The name
The system suggests the original's name with (copy) appended. Change it straight away, before you go any further. In Element the project name is what people search by, and three "(copy)" entries on the list guarantee mistakes.
The duplicate dialog: four switches on, three off
What to copy
Seven switches. Four are on by default, three are off, and that split is not arbitrary.
On by default, because this is the skeleton of the process:
Automatic messages in stages — all the automation you set up on the stages.
Job description — the text the candidate sees.
Application form + GDPR consents — together, under one switch. That matters: the form and the consents travel as a pair, because a form without consents has no right to collect data.
Project custom fields — the values of your fields and tags.
Off by default, because these concern people rather than configuration:
Sharing / participants — who has access to the project. Think before you switch it on: a new recruitment often has a different hiring manager than the previous one.
Job ads — copies of the adverts. Remember that a copied advert still has to be published separately.
Active candidates — see below; this is the only switch that moves personal data.
Candidates: what exactly happens
Switching this on copies active candidates — rejected ones are left out — at their current stages. That means three things worth knowing in advance:
without history — in the new project the candidate's activity timeline starts empty, so notes and the course of the original process will not be there,
without sending emails — moving a candidate to a stage normally fires the stage actions; duplicating does not fire them. Nobody gets a second "we would like to invite you for an interview",
the original stays untouched — the candidate is now in two projects at once, which is normal and visible on their profile.
When the button will not work
If you see a message about not having permission to duplicate this project, it means you have access to it as a participant but are not allowed to create new recruitments from it. Ask your administrator.
What duplicating will not solve
Duplicating copies a project, not company settings. Stage templates, message templates and GDPR settings are shared across the whole system, so there is nothing to duplicate — they work the same way in every project.