The Default Status List page enables administrators to configure the default statuses by organizational unit (OU), in turn defining a default applicant status workflow. A default status list can be configured for any OU level. The default list populates the Status section of a job requisition template unless the template has a custom status list. On the Default Status List page, administrators can add and remove statuses from the list, reorder the status list, and make statuses required or optional.
To access the default status list, go to. Then click the link.
To add an applicant status to the default status list, click the Add Default Status for additional information.link. See
The Status table displays all of the statuses in the default status list. The order in which they appear in the list is the order in which the default statuses appear on the Applicant Profile page. To reorder the statuses, drag and drop the statuses into the desired order and click to save the changes.Note: The position of the Closed and Hired statuses cannot be reordered.
The Type column displays the status type. For custom statuses, the status type is defined when creating or modifying the status. For default statuses, the status type is system-defined and cannot be modified.
To remove a status from the list, click the Trash Can icon to the left of the status name. Note: The Closed and Hired statuses cannot be removed.
Designate Status as Sensitive
To designate a status as sensitive, select the Sensitive option for the status. By default, there are no statuses marked as sensitive, including the Offer Letter status.
If a status is marked as sensitive in Manage Applicant Statuses, then the status appears as sensitive when configuring a requisition template. The Sensitive option can be unchecked at the template level but cannot be changed at any other point in the application process.
Checking or unchecking the Sensitive box does not affect existing requisition templates.
During the application process, sensitive statuses can only be accessed by users with permission to view sensitive statuses. The corresponding status panel on the Applicant Profile page is visible to the user but is not expandable. Note: For users that do not have permission to view sensitive statuses, the expand/collapse arrow does not appear for sensitive statuses on the Applicant Profile page.
First Advantage Integrations
For portals with First Advantage enabled for background checks, if the custom FADV custom applicant status is part of the default status list, then the status must be configured as sensitive in order to restrict access to the status.
Designate Status as Required
To make a status required by default, select the Required option for the status. When the Required option is selected for a status on this page, the status is required by default when creating a Job Requisition template. The administrator can change the Required value at the template level if necessary. Note: The Closed and Hired statuses cannot be designated as required.
Clickto implement any changes made on the Default Status List page, including any changes to the order of the statuses, required statuses, additional statuses, or removed statuses.
Clickto disregard any changes made on the Default Status List page, including any changes to the order of the statuses, required statuses, added statuses, or removed statuses.