Where Domain Blocklist Applies: Manual Add, Chrome Extension, AIRA Source & API

Domain Blocklist keeps any email on a blocked domain out of a candidate or contact record, whether that record is being created for the first time or edited later. What actually happens is different at creation time versus edit time, here's exactly what to expect at each entry point.

Across all four entry points below, the same rule applies: the profile is still created, but a blocked-domain email is stripped and not saved to the record.

If you save a new candidate or contact with an email on a blocked domain, the profile is created normally, but that email is left off the saved record.

Adding a candidate or contact from LinkedIn or another site through the Recruiterflow Chrome extension behaves the same way: the profile is added, the blocked email is stripped.

Exactly how AIRA Source handles a blocked-domain match during lookup - it strips the email the same way as other entry points.

API requests that create a candidate or contact with a blocked email domain follow the same rule as manual add: the record is created, the blocked email is stripped. See Domain Blocklist and the Recruiterflow API for more detail, including what's still unconfirmed there.

This is where Domain Blocklist behaves differently. If someone tries to edit an existing candidate or contact profile to add an email on a blocked domain, Recruiterflow rejects the change outright and shows an error naming the blocked domain, rather than stripping it silently.