Notification sender email — domain & per-user setup
Every notification Katalyz sends to your buyers (invitations, magic links, comment alerts, signature requests, etc.) goes out from a sender email address that you configure at the workspace level. There are two setups depending on your plan.
Default for all plans — a Katalyz-managed subdomain
On every plan, notifications are sent from a dedicated email address tied to your client subdomain — for example noreply@deals.acme.com. To activate it, your team needs to perform a quick DNS setup on the domain (adding the records Katalyz provides — typically MX/SPF/DKIM-style entries) so emails authenticate cleanly and don't land in spam.
Why this matters:
- Branding — buyers see your domain in the sender, not a generic Katalyz one
- Deliverability — proper authentication means emails reach inboxes reliably
- Trust — recipients are more likely to open notifications from a recognizable domain
The setup is a one-off task — once DNS is propagated, it just works for every notification going forward.
Premium plan — per-user sender addresses
On the Premium plan, you can go a step further: notifications related to a specific user (e.g. an Owner's room invites or replies) can be sent from that user's own email address. So a buyer receiving an invite from Sarah sees sarah@acme.com in their inbox, not a generic team alias.
Why this matters:
- Personal touch — feels like a 1:1 message rather than a broadcast
- Reply-to convention — buyers can reply directly to the right person; their answer lands in the user's mailbox
- Higher open rates — personal-looking sender addresses outperform team aliases
This requires each user to authenticate Katalyz with their own email provider (typically via OAuth — Google, Microsoft) so Katalyz can send on their behalf.
Setting it up
Subdomain (every plan)
Subdomain setup isn't self-serve — it goes through our team.
- Email contact@katalyz.co with the subdomain you'd like to use (e.g.
notifications.acme.com). - We generate the DNS records you'll need to add (SPF, DKIM, DMARC) and send them over.
- Your team (or IT) adds those records at your DNS provider.
- We verify once propagation has completed (usually 15 min to a few hours). The subdomain is then active and all future notifications send from that address.
For full detail (subdomain naming, sample records, security, troubleshooting) see Setting up a dedicated email subdomain.
Per-user (Premium)
Two steps: an admin enables the integration at the workspace level, then each user signs in.
1. Admin side — enable the integration
An admin goes to Settings → Integrations and authorizes the Google Workspace (or Microsoft 365) integration at the workspace level. Until this step is done, the user-side sign-in button isn't available.
2. User side — sign in with Google / Microsoft
Each user opens their profile and clicks Sign in with Google (or Sign in with Microsoft), depending on which provider the admin enabled. Once authenticated, notifications they trigger (invitations they send, follow-ups, etc.) send from their personal address.
Without a personal connection, notifications fall back to the workspace subdomain address.
See Connecting your email for the user-side flow.
What's affected
The configured sender applies to all outbound notifications:
- Room invitations
- Magic links and magic codes
- Comment / mention alerts
- Action assignment notifications
- Signature requests and reminders
- Anything else triggered by Katalyz
Related articles
Updated on: 18/06/2026
Thank you!