Skip to main content
Every org can configure a custom email sender so transactional emails (invites, reward notifications, achievement unlocks) appear to come from your brand domain. If not configured, Nudj falls back to a platform default sender.

​
Configuring a custom sender

Open email settings

Organisation Settings -> General -> Email Configuration (#1571).

Enter sender details

  • From name — e.g. “Your Brand”.
  • From email — e.g. community@yourbrand.com.
  • Reply-to — optional override.

Verify domain

Nudj provides SPF / DKIM records for your DNS. Add them to your domain’s DNS config, then click Verify.

Save

All transactional emails now use your custom sender.

​
Fallback behaviour

Orgs without custom email setup automatically use the Nudj platform default (#1671). This means:
  • Members still receive emails reliably, even if you don’t configure your own sender.
  • You can delay custom sender setup without blocking the rest of your launch.
  • Emails arrive from a Nudj domain until you’re ready to brand.

​
What emails use this

EmailTrigger
WelcomeNew member joins
Team inviteAdmin invites a teammate
Reward earnedMember earns a reward
Reward expiringAsset reward near expiry
Achievement unlockedMember unlocks an achievement
Streak reminderMember’s streak at risk
Giveaway winnerMember wins a drawn giveaway

​
DNS records

Nudj gives you three records to add:
  • SPF (authorises Nudj to send on your behalf)
  • DKIM (cryptographic signing)
  • DMARC (policy enforcement — optional but recommended)
Email deliverability improves significantly with all three configured.

​
Best practices

Use a subdomain (community.yourbrand.com) rather than your primary domain for email sending. Protects your primary domain’s reputation if something goes wrong with community emails.
Test before wide rollout — invite yourself to your org using the custom sender, verify deliverability, check that it passes Gmail/Outlook filters.