Shared inbox in Outlook: how a team actually runs one

Somebody sets up the color scheme on a Tuesday. Blue for Ana, green for Tom, orange for anything waiting on the customer. It looks great on the screen where it was built. By Thursday two people are reporting that the messages show up with no color at all, one of them can't create the category she needs, and the third has quietly gone back to just answering whatever's on top.

None of that is anyone being careless. Every convention a team lays over a shared address in Outlook (categories for ownership, flags for claiming, folders for stages, rules for routing) is a mechanism Microsoft built for one person, borrowed by five, and each one has a documented limit that nobody hits until the team is already depending on it.

This page is about that layer: the working practice, once the mailbox is already in everyone's client. If you're still trying to get it there, how to add the mailbox in each Outlook client, and the sent items default covers the click paths, and anything admin-side (creating the mailbox, granting access) is in how the mailbox gets created and who gets access. If the term itself is new, start with what a shared inbox is and when a team outgrows the built-in options. Everything below assumes three to eight people have this address open right now and need a way to work in it.

A shared inbox in Outlook is almost always a shared mailbox: one address, with no license of its own, that several people open alongside their own mail in their own copy of Outlook. Everyone sees the same messages in the same state. Nobody owns any of them until the team decides who does.

The short version

• Color categories named after people are the only assignment layer a shared inbox in Outlook gives you, and they work if you apply them when you pick a message up rather than when you finish it.
• Sharing that scheme is a permissions job, and which permissions depends on how your tenant is set up. Get that decided before you roll it out to anybody.
• Don't build the queue on unread, and don't build follow-up on flags. Neither survives a team.
• Name a duty person for the day. Every mechanism below is a convention, and conventions need somebody who owns the leftovers.

Assigning work when Outlook has no assign button

Running a shared inbox starts with a problem Outlook doesn't have a button for: there's no owner field on a message in a shared mailbox. What you have is color categories, and used with discipline they carry most of what an assignment field would do, minus the enforcement. You can see at a glance who has what, and you can filter by it.

Create them in the shared mailbox, not in your own (Microsoft's category click paths):

1. In classic Outlook, select Tags > Categorize > All Categories, then New.
2. Type the person's name, choose a color, add a shortcut key if you want one, and select OK.
3. In new Outlook and on the web, select Categorize > New category instead, name it, pick a color and select Save.
4. Manage the list afterwards at Settings > Accounts > Categories.

Reaching the shared inbox's own settings in new Outlook means adding it as an account first, which is one of the routes on the setup page.

Keep the scheme small. Five to eight categories total is the number that survives a bad week; past that people stop applying them, and a convention nobody applies is worse than none, because now the colors lie.

One rule makes the whole thing work: the owner category goes on the moment somebody starts reading properly, not when they finish. A category applied at the end of the work is a receipt. Applied at the start, it's a claim, and claiming is the thing the mailbox can't do for you.

One thing you'll see suggested elsewhere: an "Assign to" command for shared mailboxes in Outlook. Microsoft documents no such command. If someone on your team is hunting for that menu item, save them the twenty minutes.

Why your colleague sees no colors

This is the part that breaks first, and it's worth getting exactly right, because the fix depends on how your tenant is configured.

Start with what a category is. The color isn't stored on the message. Microsoft: "The list of color categories in a mailbox is stored in a hidden message in the Calendar folder of a mailbox." The message carries the category name, and the color comes from whichever list is loaded on your side, so a category that isn't in your own list turns up with a name and no color.

The permissions come from Microsoft's KB on changing categories as a delegate. Read its scope first, because this matters: it's written for delegates working in another user's mailbox folders rather than specifically for shared mailboxes, and it splits into two branches. Which branch you're in decides everything.

If your tenant is on updated Microsoft 365 calendar sharing, there are no folder permission levels to set at all. The admin grants "Exchange Full Access permissions to the sharer's mailbox", the sharer grants "Outlook Delegate Access permissions", everyone restarts Outlook, and then "the delegate can click the shared Inbox folder, then click Categorize on the ribbon." If it still misbehaves, the page's own first suggestion is toggling Work Offline on and off from the Send/Receive tab.

If calendar sharing is disabled, or the mailbox lives on an on-premises Exchange server, it's folder permissions, and they sit on two different folders:

• To apply or remove categories on items, the permission goes on the shared folder itself: right-click it, Properties, Permissions, and set "Editor or a higher permission level."
• To create or delete categories, somebody needs "Owner" permissions on the Calendar folder, and the mailbox owner sets that from their own Outlook.
• With at least Reviewer on the Calendar folder, "you can only apply categories to or remove categories from items in the shared folder based on the existing list of categories." You can use the scheme. You can't extend it.

Renaming is closed in both branches: "Only the mailbox owner can rename a category displayed in the Color Categories dialog box", and the Rename button stays dimmed for everyone else even with Owner permissions on the Calendar folder. When the access is short you get one of two errors, the more useful being "You do not have sufficient permission to perform this operation on this object. See the folder contact or your system administrator", and the New, Rename and Delete buttons all appear dimmed together.

So: one person builds the scheme once, in the shared mailbox, and before anyone rolls it out to the team, find out which branch your tenant is in. That single question saves the round trip with whoever runs your tenant, because the two answers have nothing in common. And plan around never renaming anything. You create the new category, retire the old one, and tell people twice.

Read and unread is one switch for the whole team

Every team running a shared inbox tries this on day one: unread means nobody's dealt with it. It holds for about a morning.

There's one read state per message in the mailbox, so the moment anyone clicks a message to see what it is, it's read for everybody. And people do click, because a subject line of "Re: order" tells you nothing about whether it's yours. The unread count in a shared mailbox measures how many messages nobody has glanced at, which isn't the same as how much work is outstanding, and a queue built on it quietly empties itself.

The lever you actually have is per person and it's in your own client: stop Outlook marking things read just because they passed through the reading pane. In classic Outlook: View > Layout > Reading Pane > Options, where "Mark items as read when viewed in the Reading Pane" can be turned off, or given a number in the "Wait n seconds before marking item as read" box. In new Outlook: Settings > Mail > Message handling, then pick what you want under Mark as read (reading pane options).

Be honest with the team about what that buys you. It stops your own scrolling from burning through the queue, and it does nothing about the colleague who hasn't changed the setting. Don't run the rota off unread counts. Run it off the categories.

Flags look like a claim system and are not one

Flagging is the other thing every team reaches for, partly because a flag feels heavier than a category and partly because people expect it to land in their task list. It doesn't.

Microsoft's To Do documentation is unambiguous: "Only emails flagged from your primary mailbox will sync with Flagged email folder in To Do", and "Flagged emails from shared folders and shared mailboxes are not supported" (using To Do with flagged email).

So a flag on a message in the shared mailbox is a marker inside that mailbox and nothing more. No task, no reminder, no daily list, no surface anywhere outside the folder it's sitting in. If a person's whole system for not dropping things is their flagged list, that system stops at the boundary of this mailbox, and they'll find out the hard way.

Use flags if you like them as a visual second axis, say "this one is urgent" on top of the owner category. Don't use them as the claim, and don't build a follow-up routine on them.

Folders or categories, not both

The other common way to run a shared inbox is stage folders: In progress, Waiting on customer, Done. It has one real advantage, which is that the inbox count becomes meaningful again, because handled mail leaves.

The cost is that work you can't see is work nobody chases. A message in "Waiting on customer" is invisible to anyone who doesn't think to open that folder, and if a colleague files something into a folder of their own devising it's gone from the queue entirely. Categories keep everything in one list and color it; folders empty the list and hide it.

Pick one. Running both means every message needs two decisions, and people will make them inconsistently within a fortnight. For most teams under about eight people the categories are the better bet, because the whole queue stays on one screen. The conceptual version of this argument, including what to do when neither is enough, is in the rules a team needs to write down.

Rules on a shared mailbox: where they live, and when they run

A rule you create in your own rules list won't touch mail arriving in the shared mailbox. It's not your mail, and it isn't delivered to your mailbox. The rule has to belong to the shared mailbox, which means opening that mailbox as itself.

In Outlook on the web: "On the Outlook on the web navigation bar, select your name", then "Select Open another mailbox", type the address and select Open. Microsoft notes that "Another Outlook on the web session opens in a separate window" (opening another mailbox). That window is the mailbox, so rules you create in it are the mailbox's rules. In new Outlook you get there by adding the mailbox as an account first.

Worth knowing before you build anything elaborate: Microsoft's own rules documentation doesn't mention shared mailboxes anywhere. It does spell out the trap, though, in one line about classic Outlook: "A rule with a custom action runs only on the computer where it is installed and only when Outlook is running." Custom action there means an add-in action, not a rule you fiddled with. In a personal mailbox that's a minor annoyance. On a mailbox five people share, it means a rule that fires whenever one particular colleague happens to have Outlook open and doesn't when they're on holiday, which is the kind of intermittent behavior that costs an afternoon to diagnose.

Keep shared mailbox rules boring and server side: move newsletters out, tag by recipient alias, nothing that depends on an add-in. The routing intelligence you actually want isn't a rules problem, and what a triage pass looks like per message is a better place to put that effort.

Searching a shared mailbox: one issue fixed, one still open

Search behaves differently in a shared inbox than in your own, and there are two documented problems worth knowing apart, because both look like user error when they happen.

The first one is fixed. Searching with the Current Folder scope in an automapped shared mailbox used to return "Showing results from all folders. No results found in current folder." Microsoft's status note reads: "The Outlook Team made a change from the service on 1/23/2024 to address the issue. If you don't immediately see the issue resolved, please restart Outlook to pick up the change" (the current folder search issue). So if you see this today, restart Outlook first. That's a genuinely useful answer here, which is not a sentence anybody enjoys writing.

The second one is still open, and it fires on exactly the thing this article just told you to do. Microsoft's list of service assisted search issues for shared mailboxes carries four entries. One is fixed (an Outlook crash on shared calendar search, in Version 2510 Build 19328.20000). The one that matters here is listed as still under investigation: "Server Assisted Search does not return results when searching Current Folder scope and sorting on Categories." Same page, also open: when an item is moved, categorized or marked read or unread, the search results don't refresh, so an item stays in a result list it no longer belongs in.

Sorting by category is how you'd naturally read a queue built on owner categories. If it comes back empty, that's the known issue, not your scheme. The workarounds Microsoft gives are a registry value (DisableServerAssistedSearch) or unchecking Download Shared Folders, and the second disables cached mode for the mailbox and makes it slower. Both are admin conversations. The practical answer for a small team is to filter the message list by category instead of searching and sorting, and to know the failure mode so nobody spends a morning on it.

Who answered this, and who deleted that

Assuming sent mail is filed to the shared mailbox (that's a setting, and it's covered on the setup page), you can see the reply. What you can't see anywhere in Outlook is which colleague sent it. The From line says the shared address, because that's the entire point of the shared address.

The real answer is the audit log, and it's an admin task requiring the Audit Logs role and Exchange Online PowerShell. Microsoft's page on investigating shared mailbox activities gives the searches:

• Who sent as the mailbox: Search-UnifiedAuditLog with -Operations SendAs, the delegates in -UserIds and the mailbox address in -FreeText.
• What disappeared: -Operations SoftDelete,HardDelete,MoveToDeletedItems with the mailbox address in -FreeText.
• Who changed the routing: -Operations New-InboxRule,Set-InboxRule, again with -FreeText.

There's one trap that'll waste your admin's afternoon, and Microsoft calls it out: "Don't use -UserIds with the shared mailbox address, as this action doesn't return delegate activities performed IN the shared mailbox." Activities in the mailbox come from -FreeText; -UserIds is for activities by a named person. Two other things worth knowing before anyone promises a report: capturing MailItemsAccessed needs Microsoft 365 E5 licensing, and FolderBind auditing "tracks delegate and admin folder access only. It doesn't log shared mailbox owners browsing folders."

Read that section back as a working practice and it says something plain. If your answer to "who has this one" is a PowerShell search after the fact, you didn't have a working practice, you had an investigation.

What Outlook does carry, and what it will not

The one genuinely good coordination feature here is the @mention. Type @ and the first letters of a colleague's name in the body and Outlook offers them; the contact's "full name is included and added to the To: line" by default, and in classic Outlook you can filter the message list down to Mentioned Mail (using mentions). Requirements, since they bite in mixed environments: mentioned mail needs "Exchange Server 2016, Exchange Server 2019, Exchange Online, or Outlook.com", and the @ indicator in the message list is "only available for Exchange Online or Outlook.com."

Note what that behavior actually is. The mention adds the person to the To line, which means it's a message to them, not a note attached to the conversation. There's no internal comment in a shared mailbox. Whatever context you want the next person to have either gets typed into the customer's thread, where the customer can read it, or it goes into a chat window nobody will find in six weeks when the same customer writes back.

Why is there no Focused Inbox in my shared mailbox?

Because it doesn't sort anything here. Microsoft's FAQ answer to messages not moving is "If you're using a shared mailbox, Focused Inbox will not work. This is by design", and the same page adds that the API behind it "isn't supported for the Microsoft 365 Shared mailbox" while "Outlook for Windows currently displays 'Focused Inbox' hints for shared mailboxes. This is unexpected behavior" (Focused Inbox). So you may well see Focused and Other tabs sitting in the shared mailbox. They just aren't doing anything, and anyone whose personal triage habit runs on that split needs a category or a filter to replace it.

Where the working practice runs out

None of the mechanics above assign anything. People do. What makes this work is a small agreement written down where people can see it: one owner per thread with the category applied on pickup, a named duty person each day who owns everything uncategorized, and a scheme small enough that nobody has to think about which color to use. That part isn't an Outlook question, and the rules a team needs to write down covers the decisions, the roles and the handover note properly.

Here's the honest summary of what a shared inbox in Outlook does and doesn't give you.

Every row is a convention held in place by discipline, propped on a feature built for one person. That's fine at three people who sit together. It gets expensive somewhere around six, and the tell is always the same: the categories stop being applied on the days you're busiest, which are exactly the days you needed them. If you want that cost as a number rather than a feeling, the shared inbox ROI calculator will put one on it.

That's the point where a shared inbox tool such as TriageFlow starts to pay for itself, because assignment stops being a convention someone might remember and becomes a property of the message, with a visible owner and a comment thread the customer never sees. If you'd rather see what the heavier version of that looks like first, what changes when a message becomes a ticket walks through the trade.

Frequently asked questions

How do you assign emails in a shared mailbox in Outlook?

There's no assignment feature, so teams use color categories named after people and apply one when they pick a message up. Set the categories up once in the shared mailbox itself, and sort out the sharing permissions before you announce the scheme, because what's needed differs depending on whether your tenant uses updated Microsoft 365 calendar sharing or folder-level permissions.

Can you see who replied to an email in a shared mailbox?

Not from Outlook. If sent mail is saved to the shared mailbox you'll see the reply, but the sender shows as the shared address. The colleague's name only comes out of the Purview audit log, via a Search-UnifiedAuditLog query on the SendAs operation, which needs an admin.

Why can't my colleague see the category colors I set?

Because the color isn't stored on the message. Microsoft keeps the category list "in a hidden message in the Calendar folder of a mailbox", so a category that isn't in your colleague's own list arrives carrying a name and nothing else. Getting the list shared is a permissions question, and the answer depends on which of Microsoft's two configurations you're in.

Why don't flagged emails from a shared mailbox show up in To Do?

They're not supported. Microsoft's documentation says only mail flagged from your primary mailbox syncs to the Flagged email folder in To Do, and that flagged mail from shared folders and shared mailboxes isn't supported. A flag in a shared mailbox stays a marker in that mailbox.

How do I stop emails being marked as read for everyone?

You can't. Read state is one value per message for the whole mailbox. What you can change is your own client, so opening a message in the reading pane doesn't mark it read straight away: classic Outlook under View > Layout > Reading Pane > Options, new Outlook under Settings > Mail > Message handling.

Can you set up rules on a shared mailbox?

Yes, but not from your own rules list, or they won't see the mailbox's mail at all. Open the mailbox as itself (in Outlook on the web, select your name, then Open another mailbox) and create the rules in that window. Avoid rules with custom actions, which run only on the machine where they were created and only while Outlook is open there.

Bottom line

Set up the categories in the shared mailbox, settle the sharing permissions before you roll the scheme out, and name a duty person for the day. That's the working practice for a shared inbox in Outlook, and it's most of the value available here. Then tell the team the two things Outlook won't: flags go nowhere, and read state is shared.