Notifications and Branding

Notifications are personal to you in the active workspace. Branding is a workspace configuration that the whole team shares. A confirmed custom email domain is the branding control that now affects delivered notifications.

Notification Preferences

Open Settings → Notifications. Eigenn groups events into product categories. Each row displays only the channels that are available for that event.

Current configurable groups include activity such as:

• new transactions, payment matches, reconciliation review, disputes, payout failures, and budget alerts
• invoice paid, overdue, scheduled, sent, reminder, cancellation, refund, and recurring-series events
• new, matched, cross-currency, and needs-review Inbox items
• Vault alerts
• customer messages
• the assistant's Daily Money Briefing

Eigenn generates the available list from the product's notification registry. The list can change when Eigenn adds or removes product events.

Available channels

The page can render In-app, Email, and Push. The current configurable events use in-app, and email for selected events. No current settings event shows a push toggle.

If you save no preference for an event and channel, the Settings page treats it as on.

Change a preference

1. Expand a notification category.
2. Find the event.
3. Turn the available channel on or off.
4. Wait for the switch to save the change.

The switch updates optimistically and then reloads the server value. If the save fails, it rolls back.

Eigenn scopes notification choices to your user and the active workspace. Owners and members can save their preferences. Viewers can read the page, but the server rejects their preference writes.

How Preferences Affect Delivery

The current delivery behavior differs by channel:

Invoice and recovery emails to your customers are operational communications, not personal team-alert preferences. When you turn off your own invoice notification, you do not cancel a message that a workflow sends to a customer.

Branding Settings

Open Settings → Branding. The page stores three groups of values:

Colors and theme

• Primary Color
• Accent Color

Email branding

• Email Logo URL
• Email Header Color
• Email Footer Text
• Custom Email Domain text value

Document branding

• Invoice Logo Position: left, center, or right
• Show "Powered by Eigenn"

Owners and members can submit these branding sections. Viewers cannot do the write.

Saved Values and Live Output

Eigenn saves most fields on the Branding form now. The generated email, the invoice PDF, and the payment-portal paths do not read them.

Treat the non-applied fields as prepared configuration. Check a real generated email or PDF before you promise a brand change that your customers see.

The Company logo under Settings → General is a separate workspace identity value. When you change it, Eigenn does not populate the Email Logo URL field automatically.

Confirm a Custom Email Domain

Use the Custom Email Domain card at the bottom of Branding. It is not enough to type a domain into the Email Branding text field.

Only a workspace owner can add, confirm, or remove a domain.

1. Enter a subdomain such as mail.example.com or invoices.example.com.
2. Select Add Domain.
3. Add every displayed DNS record at your DNS provider.
4. Wait for DNS propagation.
5. Select Verify Domain.
6. Confirm the badge changes to Verified.

Root domains such as example.com are not accepted. A workspace can have one custom sending domain at a time.

A verification try has a 60-second cooldown. DNS propagation can take up to 72 hours. A successful verification shows the sender address as invoices@your-subdomain.

Eigenn uses the custom domain only after the workspace has a confirmed sending-domain record. When you save the domain text alone, you do not change the sender. Email continues to use the default sender.

Remove a Custom Domain

1. Open Settings → Branding.
2. Find Custom Email Domain.
3. Select Remove Domain.
4. Confirm removal.

Eigenn clears the workspace record even when provider cleanup must finish later. Future emails use the default sending domain. You can add another subdomain after that.

Verification Checklist

After you change notifications or domain configuration:

• Reload Notification Preferences. Confirm that the switches stay in the expected state.
• Trigger a safe event for the team. Confirm that Eigenn delivers only the expected email channel.
• Remember that a disabled in-app preference can still leave a lower-priority activity.
• Confirm that the custom-domain badge shows Verified, not only Pending.
• Examine the From domain of a real email.
• Do not assume that saved colors, logos, footer, PDF position, or Powered by choice are live without output evidence.

Troubleshoot

A notification switch turns back on

The server rejected the save, or the save failed. Confirm that you are an owner or a member of the active workspace. Then try again.

An in-app item still appeared after I disabled it

The current in-app preference lowers priority. It does not stop activity creation. Use the status controls in the notification center to manage the item.

I entered a custom domain but email still uses the default sender

Use the separate Custom Email Domain card. Complete the DNS records. Then reach Verified. The text field alone does not authorize sending.

I cannot select Verify Domain

Wait for the 60-second retry countdown. DNS providers can take much longer to publish the records.

My brand colors or logo did not change an invoice

Eigenn saves those Branding form values now, but does not show them in the output that your customers see. Use the template controls of the invoice where they are available. Then check the generated PDF.

Related Pages

• Configure Notifications and Branding
• Settings Overview
• Invoices
• Document Vault
• Assistant Automation