Help Desk

Restricted Inboxes

Limit who can see an email inbox's conversations, for example chargeback or payments mail, to chosen teams.

A restricted inbox is an email inbox whose conversations only chosen teams can see. Use it for mail that most agents should not read, such as chargebacks, payment disputes or legal requests. Everyone else in the organization never sees those conversations: not in views, the All view, search, counts, exports, customer history or live updates. Opening one by link answers as if it did not exist.

Ask Copilot to restrict an inbox, or open Settings -> Channels -> Email, open the address and, under Who can see it, choose Selected teams and pick the teams. Restricted inboxes show a lock next to their address.

Who can see a restricted inbox

WhoSees its conversations
Members of the selected teamsYes
Organization adminsAlways
Anyone else, including managersNo
REST API keysYes

Organization admins always see restricted inboxes, and so does anyone whose role can create API keys or edit users, because an API key reads every conversation in the organization and editing users includes adding yourself to a team. A custom role can grant See restricted inboxes (conversations:read-restricted) for the same access. Selecting no teams leaves the inbox to organization admins only.

Only people who can see restricted inboxes can change which teams see one, so a manager cannot lift a restriction to read the mail.

The primary inbox can't be restricted, because it also sends email for conversations from other channels. Make another inbox primary first.

What else changes

  • No merging across inboxes. Mail to a restricted inbox only joins that inbox's own threads, and other inboxes' mail never joins a restricted thread. This covers the same-sender merge and replies matched by email headers. A customer replying to a support email at the restricted address starts a separate conversation. Agents can't merge conversations across a restricted inbox either.
  • Assignment. A conversation can only be assigned to someone who can see it. Automatic assignment only assigns a restricted conversation through an assignment rule that targets one of the selected teams or a person who can see it; otherwise it stays unassigned.
  • AI replies are a separate setting. Turn off AI replies on the inbox if the bot should not answer this mail.

Copilot, MCP and REST

Set restrictedToTeamIds with update_email_inbox or PATCH /rest/v1/email-inboxes/{inboxId}; see Email Inbox Settings. null opens the inbox to everyone. Team IDs come from list_teams.

MCP and Copilot follow the signed-in person: their conversation tools leave out conversations that person cannot see.

Not covered yet

Metrics and reports still count restricted conversations, and notifications, webhooks, Python actions and the REST API are not filtered. In MCP and Copilot, bot QA results and response debugging looked up by message still include restricted conversations, and Copilot users can reach webhooks and Python. Restrictions apply to email inboxes only; web chat, social and phone channels have no restriction yet.

On this page