Two people search for shared mailbox permissions and get opposite answers, because one runs Microsoft 365 and the other runs Google Workspace. The word covers three grants on a Microsoft mailbox and three separate arrangements on Google. The platform comes before the answer.
On Microsoft 365, Full Access opens the mailbox and lets someone read and manage what is in it. Send As sends mail that appears to come from the shared address alone. Send on Behalf sends from the shared address and puts the person’s name in the From line. Google Workspace has no shared mailbox object to grant anything on, so the equivalents are a delegated account, a role inside a Group, and Gmail delegation.
The Microsoft 365 permissions, and what each one does
Microsoft documents the three grants on one page, and they do not overlap (Manage permissions for recipients in Exchange Online). Full Access is the read half. Send As and Send on Behalf are the send grants, and neither grants read access.
| Permission | What it grants | Sends mail | What the customer sees |
|---|---|---|---|
| Full Access | Opens the mailbox, and view, add and remove its contents | No | Nothing. A reply is unchanged |
| Send As | Sends as if the message came from the shared address | Yes | The shared address, with no trace of the individual |
| Send on Behalf | Sends from the shared address on behalf of the mailbox | Yes | “Dana on behalf of [email protected]” |
If someone holds both send grants, Send As is the one that is used, which removes the name from every reply they send.
Who can add a member to a Microsoft 365 shared mailbox
Membership is an admin job. The members are the people who see the incoming mail and the outgoing replies, and a user with an Exchange admin role adds them in the admin center (Create a shared mailbox).
A shared mailbox supports a maximum of 25 users, and only people inside your organisation can use it (About shared mailboxes in Microsoft 365). There is no shared password either. Every new shared mailbox has sign-in blocked, and Microsoft’s guidance is to leave it blocked.
A member administers their own view of the mailbox, not the members list. Send As and Send on Behalf also need the mailbox visible in the global address list, so hiding it breaks sending from the Outlook desktop client.
What a member has to do before the mailbox appears
Nobody signs in as the shared mailbox. Each person signs into their own mailbox and adds the shared one to their Outlook profile (Open and use a shared mailbox in Outlook).
Automapping is on by default, so the mailbox appears in the folder pane after they restart Outlook. If it has not appeared a few minutes after the grant, they restart again, then add it by hand.
One consequence catches teams that grant access through a mail-enabled security group: automapping is set on the user’s mailbox and does not work for a group grant, so everyone in the group has permission and nobody gets the folder automatically.
There is no shared mailbox product on Workspace
A Google reader lands on the wrong half of every Microsoft answer, because Google Workspace has no shared mailbox object to grant anything on. How to set up a shared inbox in Gmail walks the setup for each arrangement.
| Arrangement | How access is granted | Sends mail | Where the account lives |
|---|---|---|---|
| A delegated account | The owner, or an admin, adds delegates | Yes, and the delegate can read and delete too | A user account with its own credentials |
| A Group | Membership with the owner, manager or member role | Yes, from the group address, under the posting permission | A group address, read in Google Groups or in each member’s Gmail |
| Gmail delegation | The owner grants access from Gmail settings | Yes, from the owner’s account | The owner’s own Gmail account |
Delegation, and the password the delegate never sees
A delegated account is the closest thing to a shared mailbox: one account with more than one person granted access to it. It has its own password, and the delegate never sees it.
A delegate can read, send and delete messages in that account. They cannot chat from it or change the password, and account-level settings and features that touch non-email services are unavailable to them (Delegate and collaborate on email).
Sending is where the Microsoft parallel breaks, and it breaks in the reader’s favour. A Workspace admin decides whether a message sent by a delegate shows the account owner only, or the owner and the delegate (Delegate a user’s email address).
A personal account takes up to 10 delegates and a work or school account up to 1,000, with around 40 concurrent users typical.
Group roles, and who is allowed to post
A Group is the arrangement that maps onto role names. An owner holds every permission for the group. A manager holds all of them except two owner-only actions: promoting another member to owner, and changing an owner’s role or subscription settings. A member starts with basic permissions (Create a group).
Posting is a separate setting from the role, which is the part Microsoft readers miss. “Who can post” decides who can send to the group email address, and “Who can post as group” covers sending from the group’s own address (Set permissions for managing members and content).
Taking or assigning a conversation in a Collaborative Inbox needs “Who can moderate metadata”, while marking one as no action needed or a duplicate needs “Who can moderate content” (Use a group as a Collaborative Inbox).
Gmail delegation, and what a delegate cannot do
Gmail delegation, the third arrangement, is a grant on one person’s account. The delegate accepts an invitation that expires after a week, then reads, sends and deletes mail in the account. Delegation is access rather than a queue: two delegates see the same unread list with no sign that the other has opened a thread, which Gmail delegation versus a shared inbox works through.
What to set for a team of five
Five people on [email protected], on Microsoft 365, and the settings are short.
- Full Access for all five. The mailbox is the record, and there is no reason to hide it from the people answering.
- Send As for the people who correspond as the company. This suits a public support address, because the customer wrote to the company.
- Send on Behalf for anyone whose name should appear. Use it where the customer should know which person helped.
- Keep the mailbox visible in the address list. Hide it and both send grants stop working in the Outlook desktop client.
- Keep one admin, and keep sign-in blocked. Membership is an admin action, so the team needs one person who can add and remove.
On Google Workspace the equivalent is a delegated account for the same address with the five added as delegates, or a Group where all five hold a role that includes posting. A Microsoft mailbox belongs to nobody, so a reply has no personal owner. A delegated account belongs to a person, and everyone else is a guest in it.
The two mistakes that cause real incidents
Send As where Send on Behalf was wanted. Send As makes every reply indistinguishable from one written by the company, so the customer never learns which person helped them. Send on Behalf labels the message with a name, so the customer can ask for the same person again. A billing address usually wants Send As. A five-person support address often wants Send on Behalf.
Full Access with no plan for unattended mail. Full Access is the grant everyone adds first. It solves reading, and it says nothing about the message that arrives on a Saturday. No mailbox permission creates an owner, a status or an age, so five people in a release week leave a mailbox nobody opens. The fix belongs to the arrival side, which is what shared mailbox rules covers, and to whether the team wants a queue with an owner rather than a folder with readers, which is the choice shared inbox versus help desk exists to make.
Where Chirp changes the access model
Chirp is a shared inbox for small software teams that track their work in Linear, and it connects to Gmail, Google Workspace or IMAP rather than replacing the mailbox. The mailbox stays the source of record, so replies leave from the address the customer wrote to.
The difference is in the grant. Chirp sets access per inbox with three roles: Admin, Agent and Viewer. Someone can answer support@ without automatically reading billing@, and the server checks that on every read rather than trusting a client setting.
A thread also carries an owner and a status, which is what a permission cannot hold. Linking one to a Linear issue with i means the customer hears when the fix ships.
Next step
Shared mailbox rules covers what is worth automating on the address once the permissions are right, and where both platforms stop.
FAQ
What is the difference between Send As and Send on Behalf?
Send As sends the message as the shared address with no indication that someone else sent it. Send on Behalf puts a name in the From line, so the recipient sees the person and the mailbox.
Does Full Access let someone send from a shared mailbox?
No. Full Access opens the mailbox and lets the person read and manage its contents. Sending needs Send As or Send on Behalf as well.
How do I check shared mailbox permissions in Outlook?
The grants live on the recipient, not in a mailbox folder. An admin reads them on the mailbox delegation screen in the Exchange admin center. A member sees their own folder pane, not who else holds a grant.
Who can add members to a shared mailbox?
A user with an Exchange admin role, from the admin center. A member cannot edit the list, which is the list of people who see the incoming mail and the replies.
What happens to a shared mailbox when someone leaves?
The permissions do not expire with the account. Someone with an Exchange admin role has to remove the person from the members list and from any send grant.
