Custom Entity-Type Fields empower recruiters to tailor their CRM and ATS to fit their unique workflows by linking key records like Candidates, Jobs, Contacts, Companies, Deals, Users, and Teams. These fields streamline data management, boost visibility across connected entities, and enhance automation and reporting capabilities across platforms.
This feature brings the flexibility of creating multi-select searchable fields that connect entities, ensuring data integrity, consistency, and a major productivity boost — especially when used with automation tools like API, Zapier, and Webhooks.
🧩 How to create an Entity Type Custom Field
You can create and manage custom fields linking to Candidates, Contacts, Companies, Jobs, Deals, Users, and Teams.
Please note that this is supported on Candidates, Jobs, Contacts, Companies, and Deals.
1. Go to Admin Settings and refer to the section 'Data Customization'. Select Candidate, Company, Contact, Deal or Job Fields:
2. Now, click on 'New Custom Field', name your field, and then on 'Field Type', choose between Candidates, Contacts, Companies, Jobs, Deals, Users, and Teams.
3. There you go! You have created your field and now can see it on the record type selected.
You can also add those fields to the Profile View:
And to the List View:
Hope this helps! 😃
FAQs
Why are these fields only multi-select and not single-select?
Why are these fields only multi-select and not single-select?
Multi-select ensures users can associate multiple related records (e.g., multiple candidates to a job) for richer data linking and flexibility.
Why are some fields not clickable?
Why are some fields not clickable?
For User and Team fields, profile viewing is restricted for privacy and security. Clicking is disabled to avoid exposing sensitive team/user info.
Can I search records I don’t have access to?
Can I search records I don’t have access to?
No, if you don't have access to view a record, you won't be able to search it.
Why can’t I use placeholders with these fields?
Why can’t I use placeholders with these fields?
Placeholder support is intentionally excluded since entity fields are structured references rather than free-text entries.
What happens if an imported value doesn't match any record?
What happens if an imported value doesn't match any record?
The field is skipped to maintain data accuracy. You must ensure correct slugs, email IDs, or team names are used.
Why aren’t these fields supported on the Talent Pool or Job Application settings?
Why aren’t these fields supported on the Talent Pool or Job Application settings?
These fields are meant to track internal data and are ideally not to be exposed.