Configure Notifications and Branding

Set up alerts first. Then set up the confirmed sender domain. Then test real output. The Branding page stores more values than Eigenn now applies to email and PDFs. A check 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.
• Find the DNS administrator.
• Choose a dedicated subdomain such as invoices.example.com.
• Prepare a safe event that can trigger a notification for the team.

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

1. Examine the Notification Categories

Open Settings → Notifications. Expand each category. 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 read the assistant digest

Eigenn generates the list from current product events. Not every category shows 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 that you expect to read in the notification center.
3. Wait for each switch to complete its save.
4. Reload the page and confirm the state.

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

Important current behavior:

• when you turn off email for the team, Eigenn does not deliver that email to you
• when you turn off in-app, Eigenn lowers the activity priority but still creates the activity record
• no current configurable event shows a Push switch
• the workflow controls the invoice and recovery communications to the customer, not your personal alert toggle

3. Enter Saved Branding Values

Open Settings → Branding and check:

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

Save each section independently.

These values persist on the workspace. 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 Sender 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.

Eigenn rejects a root domain. The workspace can hold one provider domain at a time.

5. Confirm DNS

1. Wait for the DNS provider to publish the records.
2. Select Verify Domain.
3. Wait at least 60 seconds before you try again, if verification remains pending.
4. Continue until the badge shows 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 keeps 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 that the intended operator gets it, or does not get it, under their preference.
3. Examine the From address and domain.
4. Check SPF/DKIM-related delivery results at the destination mailbox.
5. Open the in-app notification center and compare the activity.

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

7. Test Branding Claims Separately

Generate a real invoice PDF. Then generate a safe email preview for the customer, or a 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 confirmed sender domain applies. The other Branding form values can remain unapplied. Do not promise white-label output from a successful save toast alone.

8. Remove or Replace the Domain

To replace the domain:

1. Confirm that no critical send is in progress.
2. Select Remove Domain.
3. Confirm the warning.
4. Confirm that the next email uses the default sender.
5. Add the new subdomain.
6. Confirm the new subdomain.

Provider deletion is best-effort. Eigenn clears the workspace record so that you can add another domain.

Role Matrix

Troubleshoot

A switch reverts after a save

Eigenn cannot save the change. Confirm your role and the active workspace. Then try again one time.

In-app activity still appears

The current preference lowers priority. It does not suppress the 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. Include the 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 that Verified still appears. Delivery ignores a domain string that has no provider record. This is by design.

Colors, footer, or logo position did not change

Eigenn stores those Branding settings, but does not show them in the output that the customer sees. Use the product-specific invoice template controls. Then test the generated output.

Related Pages

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