EIGENN.
docsguidesapichangelogpricingsign in
EIGENN.

Notifications and Branding

Control personal alert channels, save workspace brand values, and verify a custom email-sending domain.

Notifications are personal to you in the active workspace. Branding is shared workspace configuration. A verified custom email domain is the branding control that currently affects delivered notifications.

Notification Preferences

Open Settings → Notifications. Events are grouped into product categories, and each row displays only the channels 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

The available list is generated from the product's notification registry. It can change as product events are added or removed.

Available channels

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

When you have not saved a preference for an event and channel, the Settings page treats it as enabled.

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 finish saving.

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

Notification choices are scoped to your user and the active workspace. Owners and members can save their preferences. Viewers can read the page but the server rejects preference writes.

How Preferences Affect Delivery

The current delivery behavior differs by channel:

ChannelCurrent behavior
EmailTeam-facing notification email checks your saved preference before sending
In-appTurning a channel off lowers the activity's priority; it does not fully prevent the activity record from being created
PushPush delivery handlers exist, but the current Settings registry exposes no push choices

Customer-facing invoice and recovery emails are operational communications, not personal team-alert preferences. Disabling your own invoice notification does 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 Canvas"

Owners and members can submit these branding sections; viewers cannot perform the write.

Saved Values and Live Output

Most fields on the Branding form are currently saved without being read by the generated email, invoice PDF, or payment-portal rendering paths.

ValueCurrent status
Primary and accent colorsSaved; not currently reflected in customer-facing output
Email logo, header color, and footer textSaved; not applied by current notification email rendering
Invoice logo positionSaved; not applied to the current invoice PDF generator
Show "Powered by Canvas"Saved; not enforced or rendered by the current customer-output path
Custom Email Domain textSaved, but not used for sending unless the domain is separately added and verified
Verified custom email domainUsed by notification email delivery when the workspace has a provider domain ID

Treat the non-applied fields as prepared configuration. Verify a real generated email or PDF before promising a customer-facing brand change.

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

Verify a Custom Email Domain

Use the Custom Email Domain card at the bottom of Branding. Typing a domain into the Email Branding text field alone is not sufficient.

Only a workspace owner can add, verify, 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.

Verification attempts have 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 verified sending-domain record. Saving domain text alone does not change the sender, and 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.

The workspace record is cleared even if provider cleanup has to finish later. Future emails use the default sending domain, and you can add another subdomain afterward.

Verification Checklist

After changing notifications or domain configuration:

  • reload Notification Preferences and confirm the switches remain in the expected state
  • trigger a safe team-facing event and verify only the expected email channel is delivered
  • remember that a disabled in-app preference may still leave a lower-priority activity
  • confirm the custom-domain badge is Verified, not only Pending
  • inspect a real email's From domain
  • do not assume saved colors, logos, footer, PDF position, or Powered by choice are live without output evidence

Troubleshooting

A notification switch turns back on

The save was rejected or failed. Confirm you are an owner or member of the active workspace and retry.

An in-app item still appeared after I disabled it

The current in-app preference lowers priority rather than suppressing activity creation. Use the notification center's status controls to manage the resulting item.

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

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

Verify Domain is disabled

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

Those Branding form values are currently saved but not reflected in customer-facing output. Use the invoice's own template controls where available and verify the generated PDF.

Related Pages

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

Marketplace Integrations

Discover, authorize, monitor, and disconnect apps that extend an Eigenn team workspace.

Onboarding and Support

Understand first-run gates, setup progress, support submission, and the recovery paths available when access or synchronization fails.

On this page

Notification PreferencesAvailable channelsChange a preferenceHow Preferences Affect DeliveryBranding SettingsColors and themeEmail brandingDocument brandingSaved Values and Live OutputVerify a Custom Email DomainRemove a Custom DomainVerification ChecklistTroubleshootingA notification switch turns back onAn in-app item still appeared after I disabled itI entered a custom domain but email still uses the default senderVerify Domain is disabledMy brand colors or logo did not change an invoiceRelated Pages

Eigenn docs

current product

Overview
Overview
OverviewAccount PreferencesAssistant AutomationAssistant Command CenterBank ConnectionsBilling and UsageBudgets and ForecastCommand CenterCustomer LifecycleCustomer RecordsCustomersDeveloper PlatformDocument Processing and ExtractionDocument VaultFinancial Analytics and ReportsFinancial OverviewInvoice InsightsInvoice ProductsInvoicesMarketplace IntegrationsNotifications and BrandingOnboarding and SupportOverviewReceivablesReceivables AnalyticsReceivables ControlsSecurity and AccessSettings OverviewStress TestsTeams and OrganizationsTone Profiles and ExperimentsTransaction Categories and RulesTransactionsWeekly Finance RitualWorkflow ExecutionsWorkflow PausesWorkflowsWorkspace Inbox and Approvals
OverviewBuild and Review a ForecastBuild Your First WorkflowConfigure Assistant OperationsConfigure Notifications and BrandingConfigure Receivables ControlsConnect Transaction RecordsCreate and Manage CustomersCreate and Send InvoicesDeveloper API SetupFirst Cash ReviewInvoice Collection WorkflowMaintain Transaction RulesManage Security and BillingManage Team AccessManage the Invoice LifecycleMCP WorkflowsMonitor and Recover WorkflowsOrganize and Share DocumentsProcess Inbox ItemsReconcile and Categorize TransactionsReview a Customer Finance RecordRun a Finance Operating ReviewRun a Receivables Tone ExperimentRun a Runway Stress TestRun Your First Command Center ReviewSet Up a WorkspaceTroubleshoot Account AccessWebhook DeliveryWeekly CFO Review
OverviewIntegrationsMCPSDKsWebhooks
OverviewAuthenticationBank Accounts APICustomers APIErrorsForecasts and Stress Tests APIInvoice Payments APIInvoices APIPaginationRate LimitsTransactions APIWebhooks API StatusWorkflows API Status
Overview
Overview