Skip to main content

Project Templates

Create a unified workflow for your recruitment team

J
Written by Jaanika Luik

Project Templates

Project Templates enable recruiters and HR team leaders to set Project Templates for future projects. It provides a way to define a common workflow for all recruiters.

User access

Who can see, create and edit Project Templates depends on the user's role. In Users & permissions → Roles, the Project templates permissions can be set separately for Team templates and Global templates: "can view" or "edit and create".
Users whose role can only view templates can still start new recruitment projects from them, but they can not edit the Template itself.

Project Template Settings and Analytics

  • Project Templates are excluded from statistics.

  • You can not import candidates into a Project Template.

  • You can not add members to a Project Template.

Creating a new Project Template

By clicking "+Create" button on the Projects page, you can choose to start creating a new Project Template.

It will open the Edit Project Template view to add Basic details and setup Stages for the Template:
​

Saving a Template looks similar to the Edit Project view with some differences:

  • Project Template does not have an End or Start date

  • Project Template does not have a Status (in progress; finished; etc)

  • Project Template can not have additional Project members

  • Categorizing all added stages is required

After Saving and entering your Project Template view, you will notice further simplifications:

  • It doesn't have activity menus as a template will not contain candidates.

  • It doesn't have Job Ads or Project Statistics menus.

Project Templates allow adding automated stage actions. This helps you to create a candidate journey and an expected recruitment pipeline timeline for your organization. Initiating a project from the template will bring over added automations.

The only limitations to adding automated actions in a template are:

  • It is not possible to add actions that run at a specific time in the future.

  • It is not possible to add the interview scheduling automatic action.

Sending Automated Emails from a Service Account

In Teamdash, you can set automated project messages — such as thank you for applying or an automated rejection email — to be sent from a service account instead of an individual recruiter. By default, the sender is the project manager, but you can always change it to a service account.

Why use a service account?

Using a service account helps ensure that all communication with candidates comes from a consistent and professional email address, for example, [email protected]. This creates a smooth and reliable candidate experience and supports your employer branding.

You can learn more about service accounts and how to set them up here.

How do I set it up and what happens if I clone the project?

To set up and explore the different options for creating automated stage actions, see here.

When you create a new project from a template or clone an existing one, messaging actions — including message, video message, and video interview — that are set to send from a specific user (for example, a service account) will remain linked to that same account.
This means your automated emails will always come from the correct sender, and you won’t need to manually adjust it for each new project.

💡 Example:
If your project template includes an automatic thank you for applying email that sends from [email protected], the new project created from that template will continue to send this email from the same address.

Initiating a new Project from the Template

Initiating a new Project from a Project Template is available through different views.

You can enter the Templates tab on the Projects page and click on the Template Card menu:

In addition, the "+ Create" button on the Projects page with the "Project" option will now automatically offer existing templates. You can decide if you wish to take a Template as the basis or start a new project entirely:
​

Select the template in the left column. Then choose a job profile to fill in the project details, or click "Start project based on template data". The Basics tab is filled in from the template, and the stages and actions are created based on the template. Check the details and click "Create project". The project will include all automated actions that exist in the template.

What's the difference between using a Project Template and Cloning an existing project?

The stages and actions are copied using a similar logic as when cloning a project, with some decisions made for the user:

  • The stage visibility settings (show/hide to limited users) are automatically copied over.

  • The actions are automatically copied over. The actions that run under a specific user will be copied to run under the new project manager, as is the behaviour during cloning.

You can Edit visibility settings and Automated actions after saving a project from the template.

Did this answer your question?