Emails
Mail is now an Explorer-owned workspace, not a standalone side tool.
What users actually see
In the current shell, users reach mail through Explorer:
- a top-level Emails branch
- a unified inbox view
- per-account inbox shortcuts under the mail branch
- optional pinned mailbox shortcuts
Older mail routes still exist in places, but they redirect back into this Explorer-owned flow.
What Email is good for
- triaging shared or operational mailbox traffic
- switching between accounts without losing repo context
- archiving messages or attachments into the right SynckHub folder
- turning email work into notes, tasks, or case updates
Safe working pattern
- Triage the message in the inbox surface.
- Decide which folder, company, contact, or case owns it.
- Archive or save it into SynckHub instead of leaving it as private inbox context.
- Create the follow-up task, note, or case action in the same workspace.
Important behaviors
- the mail branch can show unread counts
- mailbox-specific shortcuts are real workspace shortcuts
- drag or save actions can move email context into repository folders
- provider-backed search may be available separately from repository search
Guardrails
- Do not treat mailbox location as the durable source of work ownership.
- Avoid copying email context into disconnected notes when archive-to-Synck is the better path.
- If mail is not visible, the deployment likely does not have connected accounts enabled for you.