Skip to main content

Recruitment Setting

Recruitment Setting is the company switchboard for the whole module. It names the login the public careers page uses when it files an application, and it lets you make a field on any recruitment screen mandatory, read only or hidden for this company alone.

Where
Recruitment & Onboarding › Setup › Recruitment Setting
Who uses it
The implementation consultant, once per company
When
First screen of the module, before anything else is set up
Needs first
Legal Entity

What it is for​

Two jobs live on this screen and they are unrelated to each other.

The first is the careers page. When a candidate fills in the public job form, something inside PeopleNest has to write that application down. It writes it as the login named here. Leave this blank and the careers page has nowhere to put what candidates send it.

The second is field behaviour. Every recruitment screen ships with the same set of fields for every client, and clients do not agree about which of them matter. One wants Years of Experience compulsory on the Applicant. Another never asks for it and wants the box gone. Rather than branching the product, you record the difference here, naming the screen, the field, and what should happen to it. The change applies to this company only.

There is exactly one record per company. You do not create a second one.

Every field, in plain words​

Company​

FieldWhat it meansWhat to put in itNotes
Legal EntityThe company these settings apply toTariq Textile Mills LimitedRequired. Fills itself from the company you are signed in to. You do not type it, and you cannot hold two records for one company.

Controlling​

FieldWhat it meansWhat to put in itNotes
Applicant Portal UserThe single login the public careers page signs in as when it registers a candidate or files an applicationPick it from the list, for example the portal service login created for Tariq TextileLeave it blank and nothing a candidate submits on the careers page reaches PeopleNest. The list offers only company and consultant logins, not ordinary employee logins.

Default Parameters​

One line per field you want to behave differently at this company.

FieldWhat it meansWhat to put in itNotes
ScreenWhich recruitment screen the rule applies toPick it from the list, for example Recruitment ApplicantPick the screen first. The Field list then offers only that screen's fields.
FieldThe field on that screen you are changingPick it from the list, for example Years of Experience
ValueThe value the field should start with when the screen is opened fresh0Leave blank if you only want to change whether the field is compulsory, locked or hidden.
Is MandatoryTick to refuse the save until this field is filledTicked for Years of Experience
Is DisableTick to show the field but stop anyone typing in itUntickedUse this with Value when the number is a company policy nobody should override.
Is HiddenTick to take the field off the screen altogetherTicked for Current Salary at a client who does not ask candidates about payA hidden field cannot also be mandatory, or nobody can save.

Validation​

One line per extra rule you want checked on a recruitment screen before it saves.

FieldWhat it meansWhat to put in itNotes
ScreenWhich recruitment screen the extra rule runs onPick it from the list, for example Offer
Special ValidationThe prepared rule to runPick it from the listThe rules themselves are built elsewhere by the consultant. This screen only attaches one to a screen.

How to configure it​

  1. Make sure the company exists on the Legal Entity screen and that you are signed in to it.
  2. Open Recruitment Setting. The company is already filled in.
  3. Go to Controlling and set Applicant Portal User to the portal login. Do this even if the careers page is not going live yet, so nobody has to come back to it.
  4. Go to Default Parameters. Add one line per field the client has asked to change. Pick the Screen, pick the Field, then tick Is Mandatory, Is Disable or Is Hidden, and put in a Value if the field should start with one.
  5. Go to Validation only if the client has asked for a rule the product does not already enforce. Add the screen and the prepared rule.
  6. Save. The changes take effect the next time somebody opens the screen you named.

Scenarios​

"We never ask candidates what they earn now, take that box away"​

Add one Default Parameters line: Screen is Recruitment Applicant, Field is Current Salary, Is Hidden ticked. The box disappears for everyone at this company. The Screening screen has its own Current Salary field, so add a second line for it if the client wants it gone there too.

"Nobody is allowed to add an applicant without a CNIC"​

The identification lines on the Applicant screen already demand an authority, a type and a number once a line is started, but they do not force a line to exist. If the client wants more than that, this is the screen where a prepared rule gets attached under Validation.

"Two companies on one system want different compulsory fields"​

Each company has its own Recruitment Setting record, and each record only affects the company it belongs to. Sign in to Tariq Textile, set its lines. Sign in to the second company, set different lines. Neither sees the other's.

What it is connected to​

If something looks wrong​

  • "Candidates say the careers page accepted their application but we cannot see it" - Applicant Portal User is blank, or points at a login that has been blocked.
  • "A field we made mandatory is still letting people save" - the Default Parameters line names the wrong screen. The same field name exists on both the Applicant and the Screening screen and they are configured separately.
  • "A screen will not save and nobody can see which field is complaining" - a Default Parameters line has the same field both Hidden and Mandatory. Untick one of them.
  • "I cannot create a Recruitment Setting record, it says one already exists" - it does. There is one per company and you edit it, you do not add to it.