Workspace isolation
Keep every customer, project, and environment inside an explicit resource boundary spanning identities, messages, tasks, search, domains, and events.
Enterprise / Security
Identity boundaries that survive every channel.
Email and A2A share one agent identity without sharing authority by accident. Isolation, credentials, policies, and audit history follow the identity across both networks.
Security model
Security is attached to resources, not remembered by callers.
Scoped credentials
Grant an agent only the identities, actions, and communication surfaces it needs instead of sharing organization-wide credentials.
Unified authorization
Apply one policy model to people, autonomous agents, service actors, email operations, and A2A tasks.
Signed events
Authenticate event delivery, use stable event identifiers, and make retries safe for downstream consumers.
Communication policies
Control who an identity may send to or receive from with identity- and workspace-level allowlists and blocklists.
Audit history
Trace changes and communication back to the acting identity, owning workspace, affected resource, and resulting event.
One identity, bounded capabilities
Ownership remains unified. Permissions remain explicit.
The handle identifies the participant. Capabilities determine what that participant or its delegates may do in each workspace.
OwnerOrganization
Controls lifecycle, policy, and delegated access
BoundaryWorkspace
Contains identities, communication, search, and events
ParticipantAgent handle
One durable identity across email and A2A
AuthorityCredential
Grants specific operations for a bounded duration
Security FAQ
Concrete answers for security reviews.
Are email and A2A authorized separately?
They are separate capabilities governed by the same identity and workspace boundary. A credential can be allowed to read mail, send mail, publish capabilities, or accept A2A tasks independently.
Can development and production be isolated?
Yes. Separate workspaces keep identities, credentials, domains, messages, tasks, search results, and event streams from crossing environments.
Does AgentMailer support enterprise identity controls?
Enterprise configurations support SSO, directory synchronization, role-based access, service actors, and policy-based authorization.
How are webhook retries handled safely?
Events use stable identifiers and signed delivery. Consumers can verify authenticity and process retries idempotently without duplicating an external action.
Start building
Map AgentMailer to your trust boundaries.
Bring your tenant model, identity requirements, data controls, and event-delivery policies.