Branded company email
By default HridaOne sends transactional mail — credentials, payslip notices, approvals — from the platform's own SMTP identity. A company can instead send from its own domain, so an employee gets HR mail from hr@acme.com rather than a platform address.
Configured by the Super Admin on Email Settings, delivered over AWS SES.
What you set
| Field | Example |
|---|---|
| Email domain | acme.com |
| Sender email | hr@acme.com |
| Sender name | Acme HR Team |
| Reply-to | noreply@acme.com |
Verification lifecycle
NOT_CONFIGURED → PENDING_VERIFICATION → VERIFIED
↘ FAILED
On configuring a domain, HridaOne creates the SES domain identity and generates the DNS records the company's IT team must add:
| Record | Type | Purpose |
|---|---|---|
VERIFICATION | TXT | Proves domain ownership to SES |
SPF | TXT | v=spf1 include:amazonses.com ~all — authorizes SES to send |
DKIM | CNAME ×3 | Signs outgoing mail (SES uses three keys) |
DMARC | TXT | Optional — reporting and alignment policy at _dmarc.<domain> |
A 300-second TTL is recommended during setup. Once the records resolve, the status moves to VERIFIED and outgoing mail switches to the branded identity automatically. A FAILED state means a record is missing or wrong — the record list shows which.
Dispatch status
Each outgoing message has a tracked dispatch status per tenant, so a Super Admin can see whether the company's mail is actually being delivered rather than assuming it from a green "verified" badge.