Email

SEBcentral connects to any IMAP/SMTP provider (Hostinger, Gmail, Outlook, Fastmail, etc.), configured in Settings.

Personas (multiple identities, one workspace)

Each persona is one of your brands or businesses with its own mailbox (IMAP + SMTP). Manage them in Settings → Personas (add / edit / remove / set default). Each persona has a coloured avatar, a display name, and an optional signature (auto-appended in the compose box and swapped when you change the "From" persona). The app receives mail for all personas at once into one Inbox.

Connecting a persona

Three options (each persona picks one):

• Password / App password — paste an app password (most providers need 2FA on the account). Works immediately; the form has an in-app guide for Gmail and Outlook.
• Google sign-in / Microsoft sign-in (OAuth) — bring your own credentials: you register your own Google Cloud / Azure app, paste its Client ID (and secret), and click Sign in (opens your browser). SEBcentral stores the token locally and uses XOAUTH2. The form includes step-by-step setup guides. (Gmail tip: set your app to "In production" to avoid a weekly re-login that happens in "Testing" mode.)
• Assign a client to a persona (Client form → "Persona") — emailing that client defaults the "From" to its persona.
• Override per email — the compose box has a "From" dropdown (shown when you have more than one persona).
• Default order: explicit choice, then the client’s assigned persona, then the global default persona.

Inbox

• IMAP IDLE keeps the inbox live for every persona — new messages appear without polling.
• Messages are matched to clients by from-address domain or contact email.
• Each message shows a persona chip; a persona filter narrows the view to one identity.
• Search box filters by subject, sender or body.
• Attachments show as chips — click to fetch that file from the server and open it (nothing stored on disk until you click).
• Save to record — manually log any email into a chosen client/deal/project/channel’s Activity Log.
• Delete on server — bulk move to your provider’s Trash (separate from "Remove from SEBcentral").
• Compose supports attaching files.
• Folders — pick a persona, then a folder dropdown lists its server mailboxes (Sent / Spam / Archive / custom). Non-Inbox folders are browsed live from the server (read-only, nothing cached). The managed Inbox is unaffected.
• The unread count appears in the notification bell.

Mail storage model (record vs cache)

SEBcentral separates the permanent record from the working mailbox:

• Activity Log = the record. When an email is sent or received and tied to a client/deal/project/etc., its full body (with quoted reply history trimmed) is copied into that entity’s Activity Log as a standalone entry — independent of the email’s existence. Removing the email never touches it.
• Inbox = a prunable cache. Because the record is safe, the Inbox can be cleared freely to reclaim disk space. Checkboxes plus bulk "Remove from SEBcentral" (and "Remove all") wipe the cached body from your device; the email stays on your mail server. A retention rule (Settings → Personas → Keep emails in SEBcentral for 3 / 6 / 12 months / Forever) auto-removes old mail on sync and launch.

Sending

• An Email button in every entity’s activity panel opens a compose modal.
• It pre-fills the To address from client contacts (first email found) or the client’s email domain as a fallback.
• It sends from the chosen persona’s SMTP; subject and body are free-form; it supports reply threading (In-Reply-To / References headers).
• The sent message is appended to that persona’s IMAP Sent folder automatically.

Reply threading

When a reply arrives, SEBcentral checks the In-Reply-To header against stored outgoing Message-ID values. If matched, the reply is logged to both the client and the originating entity’s activity log — the full thread stays in context.