Settings → Data Model is where you shape the fields on your records. You can create
custom attributes and file types for each record type in your workspace.
Record types
The Data Model lists every record type with the number of attributes it has:
Candidates, Jobs, Applications, Companies, Contacts, Opportunities, and Files. Click a
record type to manage its attributes.
Attributes
Inside a record type, the Attributes tab lists every field. For each attribute you
can see its Type and Properties:
- System attributes are built in and cannot be deleted.
- Attributes marked AI Filled are completed automatically by AI. See
AI-filled columns.
- Starred attributes show by default on records. Unstarred attributes are hidden
behind Show all values. Drag attributes to set the order they appear in.
Use Create your own attribute to add a custom field. See
custom attributes for the data types
and how to work with them.
A custom attribute can carry a description. Write one whenever the field’s name
does not fully settle how it should be filled in: what counts as “Seniority”, which
currency a rate is in, whether a date is the start or the signature. The description is
where that convention lives, so a new colleague does not have to ask or guess.
Required fields
The Required column on the attributes list shows whether an attribute has to be filled
in, and there are two kinds.
System required
Some attributes are marked System required and cannot be changed. They are the ones a
record cannot meaningfully exist without: a job needs a Company, a Job title, and a
Status.
Warn when missing
Any other attribute can be set to warn. Open the attribute’s ⋮ menu, choose Configure
required field, tick Warn user when the field is missing, and save. The list then shows
a Warn when missing badge against it.
What the warning actually does
When someone creates a record without one of these, Spott raises a Required fields are
missing dialog naming exactly which ones, and offers Fill in fields or Add candidate
anyway.
The name of the setting is the honest one: it warns, it does not block. Anyone can
choose Add candidate anyway, and the record saves with the field empty. Use it to keep
data complete by default, not to guarantee it is.
That distinction matters downstream. A warning on Email or Nationality keeps most records
complete, but a report, a filter, or an automation that assumes
every record has one will still meet the exceptions. If something truly cannot cope with an
empty value, handle the empty case there rather than relying on this.
Files and attachments
Files are part of the data model too. You can define file types shared across
records, for example contracts or certificates, and give those types their own
attributes, such as an expiry date on a certificate. Configure them here in the same
way as record attributes. Everything is also accessible via the
API.
Consents
On the Candidates record type, the Consents tab manages the consent purposes you
can track. See consent management.