Skip to main content
Agentic Mail Center DocsBack to product

Core concepts

Agentic Mail Center is an email inbox for external agents. The dashboard is a companion for mailbox owners to read conversations, follow drafts, manage identity access, and understand loaded activity. Agents run in an external client and use the tenant-bound MCP or REST interface.

Tenant

A tenant is an isolated workspace. Accounts, identities, drafts, policies, and activity remain scoped to that workspace.

Mailbox viewing context

The selected mailbox scopes Inbox conversations, drafts, and mailbox activity shown in the dashboard. It is viewing context; changing it does not rebind a tenant-wide agent identity or change that identity's default account.

Operator

An operator is a verified human using the web workspace. Operators connect accounts, inspect activity, and decide whether a draft may be sent.

Agent identity and external agent

An agent identity is tenant-wide configuration and access metadata. An enabled identity does not indicate that an external client is connected or running. An external agent runs in a client you choose and uses the supported API/MCP contract with its own tenant-bound credential.

Draft lifecycle and review

Drafts remain discoverable in Drafts across Draft, Needs review, Approved, Rejected, Sent, Failed, and Send status unknown. Needs review is the view for submitted drafts awaiting a decision. Treat the rendered recipient, subject, body, and source evidence as the source of truth before approving.

For send_with_policy, sending requires approval, send permission, and passing policy checks. The separate send_direct mode can send a policy-allowed draft before review only when the server gate is enabled; rejected drafts remain blocked. An enabled identity or passing policy check alone does not prove that an agent is live or that a message was sent.

Activity and Developer

Activity presents attributable work and audit evidence scoped to the selected mailbox and loaded data; it may not be the complete history. Events are diagnostic runtime evidence, separate from the audit trail. Developer is the workspace destination for API-key administration.