What is the field configurator?
The field configurator is a tool that lets you decide where in the system each field added to a project will be visible and how it will behave. It is a useful function if you want to describe a project with fields other than those available by default in the system. For example, if you want to add information to a project about which system user is responsible for that project, you can do so by adding a single-choice or multiple-choice field called "Manager" and create a list of people who can be managers of that field.
Once a field is created, it can be visible in every project available in the system.
For each field, you can independently enable and disable eight options, so that the same field can, for example, be visible on a candidate's profile but not appear in the public job postings API or in the XML export.
The configurator is useful when you want to:
control which information about a project is published externally (XML, API),
organize lists of projects and candidates (what to display as a column, what can be used for filtering),
limit searching and filtering only to fields that have business sense.
Adding fields works similarly to adding application questions on an application form. You first need to add a section (it doesn't need to have a name) and then drag the selected field under the section.
Each field can have the following visibility options:
XML visibility
Decides whether the field's value will be included in the XML export (XML feeds used, among others, by job boards and external systems consuming recruitment data).
Enable if data from the field is to be transmitted externally in XML format. Disable for internal or sensitive fields.
Dashboard filtering
Decides whether the field will be available as a filter criterion on the dashboard (analytical view). Enable for fields by which you want to regularly narrow down statistics and reports (e.g., location, department, position level).
Candidate list filtering
Decides whether the candidate list can be filtered by the value of this field. Enable for fields that genuinely serve to narrow down candidates (language proficiency, experience, etc.). For descriptive text fields it is usually better to leave it disabled.
Project list filtering
Decides whether the list of recruitment projects can be filtered by the value of this field. Enable for fields describing the project (location, client, position type) by which the team often searches for projects.
Visibility on the project list
Decides whether the field will appear as a column on the project list. Enable only for key information, as too many columns make the list illegible.
Project search
Decides whether the field's contents will be included in text search within projects. Enable for fields by which people naturally search (client name, project number, city). Disabling it for long text fields speeds up searching.
Candidate profile
Decides whether the field will be visible on the candidate's card/profile. If you disable it, the value is still stored, but the recruiter will not see it in the standard profile view.
Visibility in the job postings API
Decides whether the field is made available through the public job postings API (e.g., for a careers page or another system that retrieves job postings from the platform). Enable only for data that can be publicly presented.