Connected agent identities
Assign each agent an existing provider-hosted email identity.
Run a self-hosted, single-tenant control plane for existing IMAP/SMTP mailboxes and route agent work through draft-first review. Choose metadata-only storage to keep inbound bodies, snippets, and attachment bytes with the provider until an operator explicitly loads bounded content.

Purpose-built identity, routing, and review controls. Metadata-only storage is an explicit option; full storage remains the default unless changed.
Assign each agent an existing provider-hosted email identity.
Connect existing mailboxes; AgenticMailCenter does not create or host them.
Turn received messages into workflow events.
Send email through the connected SMTP path.
Move email-driven work into automation endpoints.
Keep a visible record of events, sends, and actions.
Store provider locators and message metadata without durable inbound bodies, snippets, or attachment bytes. The Gateway never stores full MIME.
Database-backed deployments encrypt protected workflow fields with tenant-specific data keys.
Database-backed workers enforce configured retention and erasure jobs.
Deployments are invite-gated and manually bootstrapped. There is no public billing or automatic tenant or mailbox provisioning.
Request access so deployment fit and operating requirements can be reviewed.
Run one configured tenant against mailboxes you already control.
An operator supplies a setup code and explicitly bootstraps the first owner.
Use an existing IMAP/SMTP account as the agent identity.
Turn new messages into workflow events for action handling.
Send through SMTP and keep the operator audit view readable.