Start with the model
An organization contains domains and mailboxes. Dashboard users administer the service; mailbox users open only Webmail.
Understand the service before you operate it.
Follow the complete path from your first domain to a healthy mailbox and a delivered message.
01
From account to working mailbox.
Complete these steps in order so identity, DNS, and mailbox access are easy to verify.
02Your domain is the root of email identity.
Omnero Mail provisions email capability and verifies public records while you retain control of the DNS provider.
03Every DNS record has one job.
Publish the complete set. A domain is healthy only when identity, signing, inbound routing, and return-path checks agree.
04One address, one mailbox boundary.
A mailbox credential grants email access only to that full address and never grants administrative access.
05Open the mailbox, not the control plane.
Each mailbox is authenticated independently. Add the accounts you need, then switch between one address and the unified inbox without affecting the dashboard.
06Authority stays explicit.
Every administrative identity has one fixed role. Mailbox identities have no dashboard role and open only Webmail.
07Accepted is not the same as delivered.
Omnero Mail accepts work quickly and completes it through durable background processing. Status changes preserve the delivery trail.
08Every protected request rechecks the boundary.
Identity, role, organization, and lifecycle state are validated again before sensitive data or actions are allowed.
09Capacity is explicit before you need it.
The account plan defines domains, mailboxes, counted messages, and administrative seats. The API enforces the same limits everywhere.
10Start with identity, health, and status.
Most problems become specific when you confirm the surface, credential type, domain health, and latest message state.
11Build email into your product
Send, receive, inspect, and automate mailbox activity without sharing dashboard or Webmail sessions with your application.
Next step