Your sending domain
Verify your own domain so workspace emails come from your agency rather than a shared default.
Workspace emails (invites, alerts, digests) go out to your clients. By default they come from a
shared default sender. Verifying your own domain makes them come from your agency instead, for
example noreply@youragency.com.
This lives under Partner Hub > Settings > Email.
How verification works#
The page shows you the DNS records to add at your DNS provider, and gives you a Verify button to re-check the status once you have added them.
DNS changes take time to propagate, so it is normal for verification not to succeed on the first click. Add the records, give your provider time, then click Verify again.
You cannot break your own outbound mail#
This is the part worth internalizing before you start: until verification succeeds, your emails keep sending from the shared default address automatically.
There is no window where your mail is pointed at a domain that is not yet ready. Entering a domain that never verifies does not stop invites, alerts, or digests from going out. The switchover happens only once verification actually completes.
If verification is stuck#
Double-check that the DNS records shown on Settings > Email are entered at your DNS provider exactly as displayed, then click Verify again. A single transposed character is the usual cause. Beyond that, allow more time for propagation.
Throughout, your outbound mail keeps using the shared default sender, so there is no urgency beyond your own preference for branded mail.
Also on this page#
Invoice Inbox. Once set up, your clients’ carrier invoices can be forwarded to your agency’s
own inbound address, in the form {your-slug}@inbound.vigilis.io. Forwarded PDFs are parsed into
invoices automatically and appear in your Invoice Inbox.
Notification channels. Covered separately in Notification channels.
Common questions#
Our sending domain shows “pending”. Is that a problem? Not immediately. Your emails just keep using the shared default sender until verification completes. If it stays stuck, re-check the DNS records as described above.
Our sending domain won’t verify. Confirm the DNS records on Settings > Email match what your DNS provider has, character for character, then click Verify again. DNS changes can take time to propagate. Until verification succeeds, your outbound mail automatically keeps using the shared default sender, so nothing breaks in the meantime. See Our sending domain will not verify for the full check sequence.
Related guides
- Theming your instance Product name, logo, colors, and support links, plus what standard and white-label agencies each get.
- Notification channels Choose whether your agency's notifications go out by email, in-app, or Slack.
Last reviewed July 19, 2026.
Something wrong or missing? Tell us or contact support.