MailFlatDocs
Documentation/Getting Started/Dashboard tour

Dashboard tour

What every part of the interface does, and where to go for a given job.

Three modes: pick who the inboxes are for

The switch at the top of the screen changes the whole workspace. Same account, same inboxes underneath, just a different lens on them.
ModeForYou get
For everyoneReading mail yourselfThe web inbox: open addresses, read and reply, end-to-end encryption, your own domains
For agentsCode and AI agentsAPI keys, agent inboxes (always plain text), webhooks, the MCP tool spec
TestingCI and E2E suitesDisposable test inboxes tagged ci, request logs, a live API playground
Not sure which one?
If a human reads the mail, use For everyone. If code reads it, use For agents. Testing is the same agent pool with a ci tag on top, so throwaway run inboxes never clutter your agent list.

The three inbox pools

Every inbox lives in one of three pools. The pool decides whether it can be encrypted, whether the API can read it, and whether it counts toward your agent limit.

What lives in each menu

For everyoneAll inboxes · Domains · Address settings
All inboxes: your addresses and their mail. Click an address to read it; the + button opens a new one.
Domains: connect a domain you own (BYOD) and open inboxes on it.
Address settings: default retention for new inboxes, Block trackers (strips tracking pixels from HTML mail) and Lock this device (wipes the cached decryption key from this browser).
For agentsOverview · API keys · Agent inboxes · Webhooks · Tool spec
Overview: live activity and usage against your plan.
API keys: create and revoke account keys (mf_live_…).
Agent inboxes: create plain-text inboxes for automation, send a test email, or open one to inspect exactly what the agent received and sent.
Webhooks: get a signed POST when mail lands instead of polling.
Tool spec: copy the function schema for GPT, Claude or LangChain.
TestingOverview · Test inboxes · Webhooks · Request logs · Playground
Test inboxes: create run-scoped inboxes, read the OTP straight in the UI, and Tear down the whole batch when the run ends.
Request logs: the raw API calls your suite made, with status codes.
Playground: fire real requests against your own account from the browser.

Account, billing and docs

The chip in the top-right corner opens Profile (name, password, delete account), Billing (plan, invoices, upgrade or cancel) and this documentation. Signing out also clears any cached decryption key from the browser.