The Job Requisitions add-on can be added to any current subscription. The feature allows documentation of who initiates a new position, manages approvals, and supports the workflow with automated notifications. It allows hiring managers to easily signal the need for a new hire and give the recruitment team the necessary details. With job requisitions, the information and activities are all saved and tracked in one place.

This article introduces the main components of the Job Requisitions module and explains how they work together. The updated Job Requisitions module consists of three main areas:

Together, these features help you build a structured recruitment process that fits your organization's approval and hiring requirements.

Create reusable Job Profiles, Job Requisition templates, and Approval Workflows to ensure every hiring request follows a consistent process.

Job Requisitions are available to both recruiters and limited users, making it easy for hiring managers to initiate new hiring requests while following your organization's process.

Approval Workflows help ensure that every hiring request is reviewed by the right stakeholders before recruitment begins.

Teamdash can automatically:

This reduces delays and keeps the hiring process moving without manual follow-up.

Job Requisitions provide a structured process for initiating recruitment. Instead of collecting hiring information through emails or informal conversations, users complete a standardized requisition form that can include:

Teamdash allows you to create both simple and advanced job requisition workflows. You can use the built-in default flows for straightforward recruitment processes or configure more complex workflows with visibility restrictions and conditional approval paths. By combining the available settings, you can build a job requisition process that matches your organization's recruitment needs.

Before setting up job requisitions, it's recommended to map out your organization's recruitment request process.

Custom fields define the information that request submitters, such as hiring managers, provide when creating a job requisition. These fields capture the details recruiters need before recruitment can begin, such as the department, hiring reason, employment type, budget, or other organization-specific information.

Custom fields are organized into sections, and together these sections form the job requisition template that users complete when submitting a hiring request.

When adding fields to a job requisition, you can either reuse existing custom fields or create completely new ones. Linking a field means reusing a custom field that is already being used elsewhere in Teamdash, such as in Job Profiles or Projects, and making it available for Job Requisitions as well. This helps to keep information consistent and avoids creating duplicate fields which are used for the same purpose.

For example, if you already use a "Job description" and "Required Skills" fields in Profiles, you can simply link the same fields to Job Requisitions instead of creating new versions. Simply select the fields and click on the Link selected button.

You can create entirely new custom fields directly inside the Job Requisitions view without losing progress, making setup much faster and more convenient.

Templates define the structure of future job requisitions. A template can be created from scratch or from an existing Job Profile.

When creating a new template, Teamdash automatically adds all required job requisition fields to the Unassigned required fields section. These fields must be included in every job requisition and cannot be removed, but you can organize them by moving them into the appropriate sections of your template. This allows you to structure the form while ensuring that all required information is collected.

Templates support:

Open Job Requisitions from the main menu → Click + Create → Requisition template → Start with empty template

You can build a structured setup by adding sections and linking or creating new custom fields. The interface is designed to keep the initial view clean and easy to navigate, while still allowing detailed customization when needed.

For example, you might create sections for:

Sections and fields can be reordered using drag-and-drop, making it easy to adjust the structure over time.

Open Job Requisitions from the main menu → Click + Create → Requisition template → Choose the profile you would like to use as the foundation

Using a Job Profile automatically imports its sections and fields, reducing repetitive setup while still allowing additional sections and fields to be added if needed.

To learn more about Job Profiles, including how to create and configure them, see Job Profiles.

Visibility rules allow you to create dynamic job requisition forms that display only the information relevant to each request. Instead of showing every field to every user, you can control when sections and fields appear and who can access them.

Visibility rules can be configured at three different levels:

This flexibility allows you to create a single template that adapts to different hiring scenarios without creating multiple versions.

Some hiring situations require a higher level of discretion. This is a natural part of growing and changing organizations, where certain roles need to be managed carefully without disrupting established hiring workflows.

Conditional visibility determines when a section or field is displayed based on information entered elsewhere in the requisition.

You can configure rules based on:

When multiple conditions are used, you can choose whether all conditions must match or if any single condition is enough to display the field.

When a condition is not met, you can choose to hide:

This makes it easy to build dynamic forms that reveal additional questions only when they are relevant.

Example: Show the Relocation package section only when Work arrangement is set to On-site, or display Budget approval details only if Reason for hiring is New position.

In addition to conditional visibility, you can control which users are allowed to see specific information.

Fields and sections can be visible to:

Role restrictions are useful when certain information, such as salary details, internal comments, or approval notes, should only be visible to selected users while remaining hidden from hiring managers or other participants.

Approvals allow organizations to define approval workflows before recruitment can begin. Currently, approval workflows are available for Job Requisitions.

Instead of starting recruitment immediately, a job requisition can require approval from one or more stakeholders before a recruitment project can be created.

The Approvals menu consists of two tabs: Flows and Roles.

Approval roles define who is responsible for approving a requisition. Roles can later be reused across multiple approval flows.

To create a new approval role, select + Create → Approval roles. Creating an approval role consists of two steps.

In the first step, configure the approval role by defining:

In the second step, assign approvers to each role.

After approval roles have been created, they can be used to build approval flows. To create a new approval flow, select + Create → Approval flow. Creating an approval flow also consists of two steps.

The first step, Linking rules, defines when an approval flow should be applied.

Configure the following settings:

Use Linking rules to define when the approval flow should be used.

Rules here are based on requisition custom fields, allowing different approval flows to be triggered depending on the information entered in the requisition.

The second step, Stages, defines the approval process itself.

Each approval stage can be configured with:

Visibility rules can be configured so that:

Conditions can be based on teams or custom fields, making it possible to build flexible approval processes for different recruitment scenarios.

Additional stages can be added as needed, allowing approvals to be completed in a predefined sequence before recruitment can proceed.

Approval flows can include multiple stages and conditional rules. In this example, the Finance Director approval stage is only required when the Budget exceeds 10,000, allowing organizations to apply additional approvals only when they are needed.

A typical setup follows these steps:

This approach minimizes manual work, standardizes hiring across the organization, and ensures that every recruitment follows the required approval process.