If you use AI custom fields, you can now keep them in one place and control where each one applies. Scoping limits a field to the part of your organisation it's relevant to, a location or a department or specific jobs, instead of it turning up on every job you run. The AI Fields tab puts them all in one list with search, filters and bulk actions.
Before you start
To create, scope or delete AI fields you need the Create, manage and view AI fields permission.
To see them and their values without being able to change anything, you need View AI fields, but not create or manage them permission.
Permissions can be granted by your Pinpoint Admin in Company > User Management > Permissions
Scoping is built from your organisational structure, so you'll need your locations, departments and divisions set up first. Without them the scoping section doesn't appear at all.
The AI Fields tab is switched on by Pinpoint. If you have AI fields but no tab, ask your Customer Success contact to enable it.
AI fields work on applications only.
Where to find your AI fields
Step 1: Open Custom Fields
Go to Settings → Custom Fields. Alongside the tabs for your other field types there's an AI Fields tab.
Step 2: Open the AI Fields tab
Select AI Fields. Every AI field you have is listed with its Custom Field Title, Response Type and Scope.
How to scope an AI field
Scoping decides which jobs a field applies to. A field with no scope applies everywhere.
Step 1: Open the field
Click the field's name in the list, then scroll down to Scope Field Visibility.
If it's already scoped you'll see it written out in plain language under Display custom field if:, something like "Job is one of Government Assistant", with an Edit Scope button next to it. If it isn't, you get an Add Scope button instead.
Step 2: Open the scope builder
Click Add Scope. The Scope Visibility window opens on All Applications, meaning no conditions yet, so the field applies everywhere.
Step 3: Add a condition
Click Add Condition, then set the Property you're matching on (your Location, Department, Division, your own structure group, or Job) and the Operator, which is either Is one of or Is not one of.
Step 4: Choose the values
Pick one or more values: the specific locations or departments this field should apply to.
Step 5: Add more conditions (optional)
Click Add Condition again for another one. The second row lets you pick And, where every condition has to match, or Or, where any one of them is enough.
Two things to know. Whichever word you pick applies to all your conditions, so you can't mix And and Or in a single scope. And each property can only be used once, so select multiple values inside one condition rather than adding a second row for the same property.
Step 6: Save
Save closes the builder, then Save on the field itself commits it. The scope now reads back as plain language on the field, and shows in the Scope column of the list.
⚠️ Changing a scope doesn't touch values that have already been generated. Applications that newly come into scope aren't filled in retrospectively, and values for applications that drop out of scope aren't removed. Scoping only controls what happens from here on.
How to scope a field when you create it
Click Create New on the AI Fields tab and pick the type. Single Question asks one yes/no or number question about the candidate. Criteria Checklist defines several criteria and ticks or crosses each one per candidate.
Fill in the Name (up to 60 characters), the Context the AI is allowed to read (Application Answers and/or Resume), the Response Type, and the AI Prompt.
Scope Field Visibility sits at the bottom of the form, so you can set the scope before you ever save the field.
How to find fields in a long list
The Search box handles names. Filters narrows by Field Type (Yes / No, Number (Integer) or Criteria Checklist) and by Scope, so you can filter to a location, department, division or your own structure group and see just the fields that apply there.
How to change several fields at once
Tick the checkbox beside each field you want. An action bar appears telling you how many are selected, with Scope Visibility to apply the same scope across all of them, and Delete to remove them.
You can act on up to 100 fields at a time. Deletes are processed one after another, so a big batch takes a moment and shows its progress as it goes.
Bulk scope changes behave like single ones: they don't regenerate anything that already exists.
Tips
Scope early. A field scoped to one department only runs against that department's applications, which keeps job pages tidy and your AI usage down at the same time.
Leave genuinely company-wide fields unscoped. They show All Jobs in the list, so it's obvious at a glance which ones are universal.
The Scope filter doubles as an audit tool. Filter by a department and you're looking at exactly what a hiring manager there sees.
Duplicate before you specialise. Editing a field changes it everywhere it's used, so if you want a variation for one job, copy it first.
Keep prompts specific. The AI only answers from the context you selected, so asking for something that isn't in the CV or the application answers gets you nothing back.
Troubleshooting
I can't see the AI Fields tab.
Check your access group has the Create, manage and view AI fields permission. If it does, the tab probably isn't switched on for your account. Ask your Customer Success contact.
There's no Scope Field Visibility section on my field.
Your organisation has no structures set up. Scoping is built from your locations, departments and divisions, so add those first.
A field is blank for some candidates.
Usually one of three things. The field is scoped and this job doesn't match, so check the Scope column. Or the application was rejected, or its job archived, and neither of those is ever processed. Or the information simply wasn't in the context you picked, since the AI only reads the Application Answers and Resume you selected.
I widened a field's scope but older applications are still blank.
Scope changes don't backfill. Editing the field's prompt or criteria does, and that regenerates across existing applications.
A field stopped generating values.
Your organisation may have hit its monthly AI usage limit for AI fields. It picks up again on its own once there's capacity. If it keeps happening, talk to your Customer Success contact.
FAQs
If I scope a field, do values already generated for other jobs disappear?
No. Scoping affects what happens from now on. Existing values stay until the field is deleted.
Can I build "Location is London and Department is Sales, or Location is New York"?
No. Every condition in a scope is joined by the same word, either And or Or. For anything more complicated, use two separate fields.
Can I use the same property twice in one scope?
No, once each. Select multiple values inside that one condition instead.
What does All Jobs mean in the Scope column?
The field has no conditions on it, so it applies across your whole organisation.
Can I bulk-edit prompts or names?
No. Bulk actions cover scope and delete, nothing else.
If I delete an AI field, do I lose the values it generated?
If the field has generated values, those are kept. If it never generated any, it goes completely.
Can I edit a field for just one job?
Not directly, because editing changes it everywhere it's used. Duplicate the field, edit the copy, and scope that to the job.