Skip to main content

Custom sender address for subaccount notification emails

  • Updated

Note: this feature is exclusive to White Label clients.

Introduction

This article explains how to configure a custom sender email address for system notifications sent to
subaccount users. This feature allows white label clients to hide the FUGA brand and use their own email address, improving brand consistency and minimizing user confusion.

Overview

By default, notification emails (e.g. password resets, user invites) sent to subaccount users originate from a FUGA-managed domain (e.g. no-reply@fugamusic.com). Clients who prefer to maintain a white-labeled experience can configure FUGA to send these emails from a custom address on their own domain. This setup requires DNS access and domain ownership verification.

Requirements

  • You must have access to update DNS records for the sending domain.
  • The user performing setup must have the Organization management permission.

Step-by-step Setup Instructions

  1. Open the configuration wizard
    • Navigate to My organization > Subaccount notification emails.
    • Click Configure custom email address.

  2. Enter the desired email address
    • Input the email address you wish to use as the sender for subaccount notification emails.
    • This address must be hosted on a domain you control.

  3. Update the domain's DNS records
    • FUGA will display the necessary DNS entries, including ownership verification, DKIM, and DMARC records.
    • These records are required to authenticate your domain and prevent emails from being flagged as spam.
    • We only require that domains have a DMARC policy; it can be set with p=none in relaxed mode, which indicates that email that fails should be delivered normally. It may also be set to a stricter mode.
    • Important: If using Cloudflare or similar services, ensure that CNAME records are set to DNS only (not proxied).
  4. Verify DNS configuration
    • After updating the DNS, click Verify domain.
    • The system will confirm if the domain has been correctly authenticated.
    • Once verified, all subaccount notification emails will be sent from your custom address.

Updating or Removing the Custom Email Address

To update the sender address:

  • Go to My organization > Subaccount notification emails.
  • Click Remove custom configuration, then restart the wizard with a new email address.

To remove the custom configuration entirely:

  • Click Remove custom configuration. Emails will revert to being sent from a FUGA-managed address (e.g. no-reply@fugamusic.com).

Frequently Asked Questions

Which email address can I use?
Any address on a domain that you own or control. Public domains (e.g. @gmail.com) are not supported.

Can I update my email address later?
Yes. Remove the current configuration and restart the setup using the new desired address.

What happens if I do not use this feature?
Emails to your subaccount users will continue to be sent from FUGA's default domain. This may reveal FUGA’s identity to recipients.

Why is domain validation required?
Without proper DNS authentication, emails may be rejected or marked as spam. Validation confirms permission to send on behalf of the domain.

What happens if DNS authentication fails later?
Emails may fail delivery or go to spam. Clients should monitor domain configuration regularly.

Which emails use the custom sender address?

  • Emails to subaccount users: Sent from the custom domain.
  • Emails to primary accounts and standalone users: Sent from FUGA (e.g. @fugamusic.com).

How does FUGA keep its identity hidden?
Emails use the client’s configured sender address and name. They are sent via a third-party email delivery service (Mandrill) and do not reference FUGA.

Are there known issues with Cloudflare?
Yes. CNAME records must be set to DNS only. Proxied entries will cause verification to fail.

 

Need Help? Contact your FUGA representative or reach out via our support channel at support@fuga.com.

Related articles