Cloning a project lets you spin up a new project that inherits all the settings from an existing one, so you don't have to rebuild from scratch every time you open a similar role.
When to use this
If you regularly run the same kinds of searches and your projects share the similar settings, cloning saves you the setup work. Build your project once, get it dialed in, then clone it for every future req of that type.
How to clone a project
1. Open your Projects list. From the dashboard, head to your list of projects.
2. Find the project you want to clone. Click the three dot menu on the right side of the row.
3. Select Clone. A confirmation will pop up letting you know what gets copied over: project settings, stages, application form settings and team members.
4. Click OK. Your new project opens automatically with "(copy)" added to the name.
What gets copied
The new project inherits everything you've configured on the original:
Project settings
Stages and pipeline structure
Team members
Scheduling link appearance
Custom fields
Default call guide
What's different
A few things are intentionally fresh on the cloned project:
No contacts. The new project starts empty so you can add candidates for this specific req.
A brand new scheduling link. You'll see a unique URL ready to share. It still points to the same configured availability and appearance from the original.
Customizing your cloned project
Once your copy is open, head to the settings gear in the top right to:
Rename the project (remove the "(copy)" tag and give it a real name)
Edit the scheduling link (optional)
Update the scheduling link appearance
Adjust custom fields
Change the default call guide
Any changes you make to the clone are completely independent of the original project, so feel free to tweak.