Job custom fields

Where to find it

Configuration → ATS settings → Job → Custom fields tab

Who can use it

Administrators with settings access

Direct URL

https://admin.nextal.com/conf/admin/settings/ats/jobSettings/customFields

Job custom properties extend the built-in job fields with data points that are specific to your organization. If every job posting needs a cost-center code, a business-unit tag, or an internal priority level, you define those fields here and they appear on the job creation and editing form for every recruiter.

Screenshot pendingThe Custom fields tab of Job settings showing a list of custom properties with their field types and drag handles (⠿).

The Custom fields tab. Each row shows the property order, its name, its field type, its status (Active/Inactive), and an action to edit it.

Property types

Type	Best used for
Text	Codes, identifiers, short free-form labels
Number	Budget figures, headcount targets, priority scores
Date	Target start dates, posting deadlines
Dropdown	A fixed list — business units, regions, hiring tiers
Multiple choice	A fixed list where more than one option can be selected

Adding a property

Go to Configuration → ATS settings → Job and open the Custom fields tab.
Click Add a field at the top of the list: the side panel opens.
Set the Active toggle.
Choose the Type from the dropdown.
Enter the Label. If your account has several languages, the FR / EN / ES pills above the field switch language; a dot marks a language still to translate (only your account’s languages are offered).
Click Save.

The property appears immediately in the job creation and editing form.

Reordering properties

Drag the ⠿ handle of a row to change the display order; the order is saved as soon as you release it (with the keyboard: Tab to the handle, Space, arrow keys, Space). Arrange the most frequently used properties near the top so recruiters encounter them first.

Editing and deactivating

Click a row (or ⋯ → Edit): the side panel opens; Save applies, Cancel discards your changes. Only the row’s Active switch and the ⠿ handle act immediately. Deactivating a property hides it from the job form without deleting existing values — useful when a field was seasonal or project-specific and is no longer needed day-to-day.

Changing the type of a field that is already filled in can make existing values unreadable: a confirmation is asked before the change is saved.

There is no delete action for custom properties — a property can only be deactivated or reordered.

For fields of type Dropdown or Multiple choice, an “Edit values” action is available on the row. This opens a panel where you can:

Add new option — add an option to the list.
Reorder the options by dragging the ⠿ handle.
Edit Option — rename an option (per language if multi-language).
Delete Option — remove an option from the list.

Tips

Avoid duplicating built-in fields. Nextal already captures job title, location, schedule type, and contract type. Custom properties should add what is not already there.
Use Dropdown or Multiple choice for any field that feeds a report. Free-text values for structured data produce inconsistent groupings in analytics.
Coordinate with your job templates. Custom properties set on a template carry over to jobs created from it, saving recruiters time at creation.
Communicate new properties to recruiters before activating them — they appear in the job form immediately.