The Domain Blocklist stops any email on a specific domain from ever being saved to a candidate or contact profile in Recruiterflow. Add a domain once in General Settings, and Recruiterflow enforces it everywhere an email could end up attached to a record: when a new profile is created, and any time someone tries to edit an existing profile to add an email on that domain.
This is built for search firms managing off-limits agreements, non-competes, or client conflicts at scale, where checking each new record by hand against a growing list isn't realistic.
Who uses it
Only Admins can add or remove domains from the blocklist, from General Settings. Once a domain is blocked, the restriction applies account-wide, to every user, regardless of role.
What it does
When a new candidate or contact is added with an email on a blocked domain, the profile is still created, but the blocked email is stripped and not saved to the record.
If someone tries to edit an existing profile and add an email on a blocked domain, Recruiterflow rejects the edit outright and shows an error, rather than stripping it silently.
Applies consistently across every entry point into Recruiterflow: manual add, Chrome extension, AIRA Source, and the API.
Is configured once, account-wide, so the restriction doesn't depend on individual users remembering a rule.
What this means for the profile itself
Domain Blocklist controls the email field, not the profile as a whole. A candidate or contact can still be created and exist in your database without any email attached, if the only email offered for them was on a blocked domain.
What it's not
Domain Blocklist is not the same as Off Limits, which restricts outreach to candidates already in your database rather than stripping their email. See Domain Blocklist vs. Off Limits: What's the Difference? for a full comparison.
Getting started
See Setting Up the Domain Blocklist to add your first domain.