This article explains how Humanforce HR (intelliHR) handles email authentication, sending, deliverability, and data protection.
Key points
- Authentication: SPF, DKIM, and DMARC are implemented. Emails are DKIM signed. See the quick header check below.
- Sending: HR uses shared Amazon SES IP ranges. Custom domains or subdomains are not supported today.
- Data protection: Each customer has a separate database schema. Email processing is per schema. Replies to donotreply@intellihr.net are archived and not monitored.
Authentication and signing
Humanforce HR uses SPF, DKIM, and DMARC. Emails are signed so receiving systems can verify authenticity.
Quick header check
Authentication-Results: dkim=pass header.d=intellihr.net; dmarc=pass header.from=intellihr.net; spf=pass smtp.mailfrom=donotreply.intellihr.net
How to verify: Open the message headers in your mail client and look under Authentication-Results for dkim=pass, dmarc=pass, and spf=pass.
Sending infrastructure and deliverability
HR sends via Amazon SES using shared IP ranges. Amazon SES uses dynamic IP ranges. Where possible, allowlist by domain and authentication results, rather than IP.
Spoofing and phishing protections
HR uses SPF, DKIM, and DMARC to protect sender identity and message integrity. Modern email providers, such as Microsoft 365 and Google, require these protections.
Inbound behaviour
If a recipient replies to donotreply@intellihr.net, the message is stored in an S3 bucket for historical and auditing purposes. The mailbox is not monitored.
Customisation and roadmap
Our roadmap and future enhancements are prioritised based on customer feedback and demand. If you need either capability below, please submit product feedback through Help and Support. We review requests regularly when planning upcoming work.
- OAuth2 delegated access such as Send As is not supported. Please submit product feedback if you need this.
- Custom domains or subdomains such as hrteam@companyname.intellihr.net are not supported. Please submit product feedback if you need this.
We prioritise items with broad customer demand; adding your use case and expected impact helps us weigh priority.
Data separation and privacy
Each customer has a separate database schema. Email processing is performed per schema. This design prevents data leakage between customers, including in headers and metadata.