Your own sender domain for system emails

By default, every automatic message from Univents comes from our own address — for example "Your Company" <mail@notifications.univents.app>. With your own sender domain, quotes, invoices, enquiry confirmations, follow-up emails and staff-portal invitations come from your own address instead, e.g. events@your-company.com. Login emails (sign-in links, team invitations) always stay on univents.app.

This feature is included in the Enterprise plan, or unlocked for your workspace by Univents.

Setting up your domain

1. Open Integrations → Email and scroll to the “Sender for system emails” card.
2. Enter a subdomain, for example events.your-company.com — deliberately not your main domain like your-company.com. A dedicated subdomain protects your main domain’s reputation: any sending issues only affect the subdomain, never your regular business email.
3. Univents creates the domain and shows you three DNS records (type, name, value). Click “Copy all records” and pass them to your IT team — they add them wherever your domain is managed.
4. Once the records are set, click “Verify”. Univents also checks the records automatically every hour in the background — you’ll get a notification as soon as the domain is confirmed, even without clicking yourself.
5. After a successful check, you’ll see “Activate now”. Only this click actually switches system emails over to your domain — verification alone doesn’t activate anything.
6. Optionally adjust the sender address (the part before the @, default events) and the “Reply to” address (see below).
7. Use “Send test email” to receive a message from the new address at your own login email. Check your spam folder if needed — right after switching over, a test email can land there until your mail client learns the new address.

Instructions for your IT team

The three records are standard sender-verification practice — any IT team will recognise them:

• DKIM (a TXT record): digitally signs your emails so recipients can verify they’re genuine.
• SPF (an MX and a TXT record): defines which servers may send on behalf of the domain.
• DMARC (recommended, not required): tells mail providers what to do with emails that fail DKIM or SPF. Univents suggests p=none, which only logs failures without blocking mail.

Two notes for your IT team:

• If your domain contains accented characters, the DNS record needs the Punycode form (xn--…) — entering accented characters directly will fail verification.
• If your main domain already has a DMARC policy, it automatically applies to the new subdomain too, unless your IT team has set an explicit sp= (subdomain policy) value. This is usually not a problem, but worth knowing if your main domain runs a strict policy (p=reject) — in that case, a dedicated _dmarc record for the subdomain is worthwhile.

Checking before you click “Verify”

DNS changes sometimes take a while to propagate everywhere (the TTL, usually 5–60 minutes, sometimes longer). If you want to check whether a record is already visible yourself, use dig (Mac/Linux) or nslookup (Windows) with the name from the table:

• DKIM (TXT): dig TXT resend._domainkey.your-subdomain.com or nslookup -type=TXT resend._domainkey.your-subdomain.com
• SPF (MX + TXT): dig MX send.your-subdomain.com and dig TXT send.your-subdomain.com
• DMARC (TXT): dig TXT _dmarc.your-subdomain.com

If you don’t get an answer yet, or see an old value, wait out the TTL and try again — that’s normal and not an error in Univents.

What happens if something goes wrong?

If domain verification fails later — for example because a DNS record was accidentally removed — Univents automatically switches sending back to univents.app. No email is ever lost, and you get a notification naming the missing record. Click “Verify again” once the record is back in place — the domain then becomes active again automatically, without needing to set it up from scratch.

Who receives replies from your customers?

The “Reply to” field always shows you which value currently applies and where it comes from. The order is:

1. the address you enter yourself in the “Reply to” field,
2. otherwise your workspace’s email address,
3. otherwise your oldest connected team inbox,
4. otherwise the email address of the account owner.

If you leave the field empty, the next value in the list applies automatically.

Frequently asked questions

Can I use my main domain instead of a subdomain? No — for security reasons only a subdomain is possible. This protects your regular business email from any side effects of automatic sending.

Is this the same domain as the newsletter module? No — newsletters and system emails each need their own subdomain, for example news.your-company.com for newsletters and mail.your-company.com for system emails. Newsletters track opens and clicks; links in quotes and invoices are deliberately left untouched.

Can I remove the domain again? Yes, via “Remove domain” on the card. System emails immediately switch back to univents.app afterwards.

What about login emails? Sign-in links and team invitations always come from univents.app, regardless of this setting.