Skip to content
English
  • There are no suggestions because the search field is empty.

Manage Your Temp Workflow Settings

How to customise the settings of your Temp Job Workflow

Beta Header

To get the most out of your Temp recruitment process in Firefish, it's important to configure your Temp Workflow settings correctly.

Superusers can control how potential matches are suggested, how your availability pool behaves, and what happens when candidates leave roles. This guide will walk you through each setting so you can tailor your Workflow to suit the way your team places Temp candidates.

The Temp Workflow is currently in Beta and will be available to users shortly. 

Click the links below to jump straight to a section or keep scrolling.


You can make changes to the Workflow settings of your Temp jobs whenever necessary.

To find your Temp Workflow settings, click the cog icon in the top menu section of the page. Then, select Job Configuration from the drop down menu.

In the Job Configuration section, click on Temp Workflow.



Potential Matches

Potential Matches utilise Firefish AI to match ranked candidates to your Job Workflow - easily showing you the top candidates in your database for a particular role. 

You can find full details around Potential Matches Settings on this page

Note: The Temp Workflow has it's own Potential Match settings, however, the Candidates Contract Workflow Preferences are currently used for Potential Matches on this Workflow. 


Availability Pool

In the Availability Pool tab you'll see the options for Time Settings and Automation Rules. 

The Default Start Time setting is used to set the default start time for the availability pool. The time that is selected will be the time that the Calendar and List view load to by default. 

For example, setting this to 07:00, the availability pool will load to 07:00:

The Leavers setting controls how long a candidate stays greyed out at the bottom of the availability pool after their 'leaver date' has been reached.

  • When enabled a candidate remains greyed out for the configured period after their leaver date.

  • When disabled a candidate is removed from the availability pool as soon as their leaver date is reached.