# Shared mailbox, alias or own address for an AI agent

> Four ways to give an AI agent email: an alias, a shared mailbox, delegated access to a human's mailbox, or its own address. What each lets the agent read.

Source: https://trotta.email/compare/shared-mailboxes-for-agents

Give an AI agent delegated access or a shared mailbox when it assists humans inside mail they already own, and they review its work. Give it its own address when it acts alone, signs up for services or hears from strangers, so it reads its own mail and nothing else, and a mistake stays in one inbox.

Updated November 20, 2026

There are four common ways to put an agent on email. Three place the agent inside a mailbox that belongs to a human or a team. The fourth gives it a mailbox of its own.

## The four options

- **Alias.** An extra address on an existing mailbox. Google Workspace allows up to 30 for each user and Microsoft 365 up to 400, at no extra cost. Mail lands in the owner's inbox, and a Google Workspace alias has no sign-in of its own.
- **Shared mailbox.** One mailbox that several members open. In Microsoft 365 it needs no license up to 50 GB, supports a maximum of 25 members and is not intended for direct sign-in. In Google Workspace the nearest tool is a collaborative inbox, which is a Google Group.
- **Delegated access.** A human lets someone else into their mailbox. A Gmail delegate can read, send and delete email in the account. An Outlook delegate at the Reviewer level can read items in the owner's folders.
- **Its own address.** A separate mailbox for the agent. Its key reaches that inbox and no human's mailbox.

## Sharing a mailbox and an address of its own, side by side

|  | Alias, shared mailbox or delegated access | Its own address on Trotta Mail |
| --- | --- | --- |
| Built for | Humans sharing mail with other humans. | AI agents and humans. The guard is stricter for an agent. |
| When mail is screened | By the mailbox provider's filters, before delivery. Later checks act on delivered mail. | While the sending server is still connected, before the message is accepted. |
| What an agent can read | Alias or delegation: the owner's mailbox. Shared mailbox: what the whole team receives. | Its own inbox, in the safe view: hidden text removed, instructions aimed at a model marked. |
| Held mail and human review | The spam and quarantine rules set for the human mailbox. | Held outside the inbox. A human can release it. An agent's key cannot. |
| Outgoing checks | The agent sends as, or on behalf of, the human or the team. | From the agent's own address, screened for secrets, sensitive data and replies steered to a new address. |
| Sign-in codes | Codes and reset links sent to the mailbox are messages the agent can read. | The agent's own codes arrive in its own inbox. A human's are sealed from every API key. |
| Setup for many agents | An admin adds each alias, member or delegate. | One API call per inbox. Pods keep each customer's inboxes apart. |
| Price to start | An alias costs nothing extra. Shared mailboxes and delegation come with the provider's plan. | Free: 2 inboxes, 1,000 emails a month. Developer, $20 a month: 5 inboxes, 5,000 emails. Startup, $200 a month: 50 inboxes, 50,000 emails. |

## When sharing a human's mailbox is the better choice

- The agent drafts and a human sends, so a human sees each message.
- A team already works a shared support address, and the agent sorts and labels beside its members.
- The work depends on years of threads in the mailbox.
- The agent runs inside your provider's own assistant, under your admin's controls.

Give the least access that does the job, and check your provider's rules. Google says an account is intended for one user. Microsoft says a shared mailbox is not intended for direct sign-in.

## When its own address is the better choice

- The agent signs up for services. Its codes should not sit beside a human's password resets.
- The agent hears from strangers. If it is [hijacked](https://trotta.email/threats/agent-hijacking), it should reach one inbox, not a human's whole history.
- You want a clear record: the agent's mail comes from the agent's address, not a human's name.
- You need many agents. An address for each is one API call.

The risk with a shared or delegated mailbox is reach. A hijacked agent with a human's mailbox could ask a site for a password reset, read the email and own the account.

## A middle path: an agent in a human's mailbox, with limits

Some agents must work in a human's mailbox. In Trotta Mail, a key for a human's mailbox starts with drafts: the human sends. [Login mail is sealed](https://trotta.email/docs/security), so one-time codes, password resets and sign-in links do not exist for any API key.

## What moving looks like

1. Create the agent's inbox with one API call, or in the console.
2. Change the address on the agent's accounts, so new codes arrive in its own inbox.
3. Remove the delegate, the membership or the app permission from the human's mailbox.
4. On a paid plan, put agent inboxes on a subdomain, so the rest of your mail stays where it is.

## Questions

### Can I give an AI agent an email alias?

Yes, but an alias is another name for an existing mailbox. Mail lands in the owner's inbox, so the agent needs access to that inbox to read it.

### Can an AI agent use a shared mailbox?

It can reach one as a member or through your provider's API, within your provider's rules. It will read what the team receives, and what it sends goes out under the team's name.

### Is it safe to delegate my inbox to an AI agent?

It is as safe as the agent is hard to trick. A delegate can read the mailbox, sign-in codes and reset links included, so a hijacked agent can reach accounts that reset through that address.

### Does an AI agent need its own email address?

When it acts alone, yes. Its own address keeps its mail, its codes and its mistakes in one inbox, apart from any human's.

## Sources

- [Delegate and collaborate on email (Gmail Help)](https://support.google.com/mail/answer/138350)
- [Add or delete an alternate email address (Google Workspace Help)](https://knowledge.workspace.google.com/admin/users/add-or-delete-an-alternate-email-address-email-alias)
- [Avoid sharing an account among users (Google Workspace Help)](https://knowledge.workspace.google.com/admin/users/avoid-sharing-an-account-among-users)
- [Use a group as a Collaborative Inbox (Google Workspace Learning Center)](https://support.google.com/a/answer/167430)
- [About shared mailboxes in Microsoft 365 (Microsoft Learn)](https://learn.microsoft.com/en-us/microsoft-365/admin/email/about-shared-mailboxes)
- [Add another email alias for a user (Microsoft Learn)](https://learn.microsoft.com/en-us/microsoft-365/admin/email/add-another-email-alias-for-a-user)
- [About delegates: allow someone to manage your mail and calendar in Outlook (Microsoft Support)](https://support.microsoft.com/en-us/office/allow-someone-else-to-manage-your-mail-and-calendar-41c40c04-3bd1-4d22-963a-28eafec25926)
- [Trotta Mail API summary for agents](https://api.trotta.email/llms.txt)
- Trotta Mail docs: security model (sealed login mail, what an agent may write)

## Related

- [Agent identity and email](https://trotta.email/learn/agent-identity-email) Guides
- [Give an AI agent an email address](https://trotta.email/learn/give-an-ai-agent-an-email-address) Guides
- [Verification code theft](https://trotta.email/threats/verification-code-theft) Threat library
- [Pricing](https://trotta.email/pricing)
- [Security](https://trotta.email/security)
- [Quickstart for agents](https://trotta.email/docs) Docs

Every check is on, on every plan. Free for two inboxes. No card.

[Get an inbox](https://trotta.email/signup) [See pricing](https://trotta.email/pricing)
