Configure Notifications and Branding

Configure alerts first, then the verified sending domain, then test real output. The Branding page stores more values than Eigenn currently applies to email and PDFs, so validation is part of the workflow.

Before You Start

• Confirm the active workspace.
• Use an Owner or Member account for notification and branding-value writes.
• Use an Owner account for custom email-domain lifecycle actions.
• Identify the DNS administrator.
• Choose a dedicated subdomain such as invoices.example.com.
• Prepare a safe event that can trigger a team-facing notification.

Notification preferences are personal. Repeat the alert review for each operator.

1. Review Notification Categories

Open Settings → Notifications. Expand each category and decide whether its available channel is actionable for your role.

Prioritize:

• invoice overdue, paid, refund, and customer-message events for receivables operators
• reconciliation conflicts, payment matches, disputes, and payout failures for finance operators
• Inbox needs-review and cross-currency matches for document reviewers
• Vault alerts for contract or renewal owners
• Daily Money Briefing for operators who review the assistant digest

The list is generated from current product events, so not every category exposes the same channels.

2. Set Personal Channels

1. Turn Email on only when an email is useful outside the app.
2. Turn In-app on for work you expect to review in the notification center.
3. Wait for each switch to finish saving.
4. Reload the page and confirm the state.

When no prior choice exists, the current page shows the available channel as enabled.

Important current behavior:

• disabling team-facing email prevents that email delivery for you
• disabling in-app lowers the activity priority but does not prevent the activity record from being created
• no current configurable event shows a Push switch
• customer-facing invoice and recovery communications are controlled by their workflow, not your personal alert toggle

3. Enter Saved Branding Values

Open Settings → Branding and review:

• Primary Color and Accent Color
• Email Logo URL, Header Color, and Footer Text
• Invoice Logo Position
• Show "Powered by Canvas"

Save each section independently.

These values persist on the workspace, but the current customer email, invoice PDF, and portal paths do not read them. Record them as intended branding, not deployed branding.

Use Settings → General → Company logo for the shared workspace logo. It is separate from Email Logo URL.

4. Add the Custom Sending Domain

Use the Custom Email Domain card, not only the similarly named text field in Email Branding.

1. Enter a subdomain.
2. Select Add Domain.
3. Copy every displayed DNS record name and value.
4. Add record priority and TTL when shown.
5. Publish the records at your DNS provider.

Root domains are rejected, and the workspace can hold one provider domain at a time.

5. Verify DNS

1. Wait for the DNS provider to publish the records.
2. Select Verify Domain.
3. If verification remains pending, wait at least 60 seconds before retrying.
4. Continue until the badge is Verified.

DNS propagation can take up to 72 hours. Repeated clicks cannot accelerate it.

After verification, the card shows the effective sender as invoices@your-subdomain. Email delivery uses the domain only while the workspace retains the provider domain record.

6. Test Real Delivery

Use a non-customer, reversible team event where possible.

1. Trigger an event that has an Email preference.
2. Confirm the intended operator receives or does not receive it according to their preference.
3. Inspect the From address and domain.
4. Check SPF/DKIM-related delivery results at the receiving mailbox.
5. Open the in-app notification center and compare the activity.

Do not test customer recovery by sending an unreviewed message to a real customer.

7. Test Branding Claims Separately

Generate a real invoice PDF and a safe customer-facing email preview or test delivery. Compare:

• workspace company logo
• invoice template values
• primary/accent colors saved on Branding
• Email Logo URL, Header Color, and Footer Text
• invoice logo position
• Powered by treatment

At present, the verified sender domain applies while the other Branding form values can remain unapplied. Do not promise white-label output based only on a successful save toast.

8. Remove or Replace the Domain

To replace the domain:

1. confirm no critical send is in progress
2. select Remove Domain
3. confirm the warning
4. verify subsequent email uses the default sender
5. add and verify the new subdomain

Provider deletion is best-effort, but the workspace record is cleared so another domain can be added.

Role Matrix

Troubleshooting

A switch reverts after saving

The change could not be saved. Confirm your role and active workspace, then retry once.

In-app activity still appears

The current preference lowers priority rather than suppressing record creation.

The domain field saved but no DNS records appeared

You used the Email Branding text field. Scroll to Custom Email Domain and select Add Domain.

DNS verification remains pending

Compare every DNS record exactly, including host-name conventions at your provider. Wait for propagation and the 60-second retry cooldown.

Email uses the default sender after verification

Reload Branding and confirm Verified still appears. A domain string without its provider record is intentionally ignored by delivery.

Colors, footer, or logo position did not change

Those Branding settings are currently saved but not reflected in customer-facing output. Use product-specific invoice template controls and test generated output.

Related Pages

• Notifications and Branding
• Settings Overview
• Security and Access
• Invoices
• Invoice Settings
• Support