Omniscio

Shared Inbox for teams

An owner or admin of a Team Chat workspace opens Workspace settings and flips Shared Inbox on. That records the workspace on the Supermail backend; members, roles and invites keep coming from the workspace and nowhere else.

On this page

Where the switch lives

Team Chat, then Workspace settings, then the General tab. The switch is drawn only for the workspace's owner and admins — a member never sees it, and the backend refuses the change for anyone who is not an admin of that team. The company workspace and self-serve chat workspaces both support it.

The switch records one thing on the Supermail backend: whether this workspace's team record is switched on. It never writes to the workspace document in Firestore and it changes no Security Rules, so the phone app and the workspace's own member list are untouched.

What turning it on does

  • Creates the workspace's team record once, keyed by the workspace's kind and id (org for the company workspace, chat for a self-serve one). Flipping it on again changes nothing, and switching it back on after off keeps the same record.
  • Records the admin's own time zone at the moment it is switched on, which the business-day clock uses.
  • Never creates a second member list. Everyone's role comes from the workspace's membership, and that check runs on every request, so removing someone from the workspace takes their Shared Inbox access away with it.

The words a team shares

Every shared conversation sits in one of four states, and every screen shows them the same way: Needs reply (the ball is with us), Waiting on vendor (the ball is with them), Snoozed (put away until a date) and Done.

  • A vendor replies and a conversation that was Waiting on vendor, Snoozed or Done moves back to Needs reply. Nothing forces a conversation to Done; it can stay open for as long as the work is real. The one exception is a message a machine sent, which never moves a conversation.
  • Sending our reply moves the conversation to Waiting on vendor.
  • Every conversation starts on Needs reply, except one that opens with mail a machine sent: that one starts Done. Threads brought in by a mailbox's first 90-day import start under the import rules further down this page.

A new team starts with these settings, and an admin can change each one later:

Setting New teams start on
AI Level Drafts only — the AI drafts, a person always sends
Agreed Terms Suggest — the AI proposes a change, a person confirms it
Follow-up delay 3 business days of silence before the owner hears about it
Undo window 10 seconds to undo a send
Time zone, business hours, holidays Set by the admin when the team is switched on

Alerts follow the same rule everywhere: an owner hears about their own conversations, a mentioned person hears about the mention, admins hear about conversations nobody owns, anything overdue and any mailbox that has stopped working, and the person whose mailbox it is hears about a broken mailbox and about the one confirmation a first share needs.

Statuses, alert kinds, the AI actions and their lowest AI Level, these settings and their defaults, the mail providers and the order-sheet sources are each held in one place on the backend, and every screen and check reads that one place. A new status or a new alert kind is one change, made once.

What turning it off does

The Shared section disappears for that workspace and nothing shared runs for it. Every shared address answers "not found" for that workspace, so nothing shared is read or changed through it, with one exception: the switch itself still answers, so an owner or admin can turn the Shared Inbox back on and read that it is off. A member of the workspace sees the off state there but only an owner or admin can flip it. Every shared background job for that workspace stops before it does anything and is marked done, so no timer, alert or ingest runs behind a switched-off team. A live stream a screen already holds stops at its next check, so a closed team gets no events either. Switching it off never deletes anything: the backend marks the workspace's team record off and keeps every row. Everything already shared is kept — conversations, contacts and notes stay on the backend, and switching the Shared Inbox back on brings them back into view. Each flip is written to the team's activity, with who made it and which way it went.

The vendor list

Vendors in the Supermail navigation is the team's list of the outside companies it shares mail with. Every member can open it, and every member can add, edit and remove a vendor — the changes are the team's, not one person's.

Each vendor has a name, one or more email domains, any exact email addresses that do not sit on a company domain, and a default owner. A thread joins the shared inbox when anyone outside the team on it matches one of those domains or addresses; the default owner is who it lands on.

  • A free email service (gmail.com, outlook.com and the rest) can never be a vendor domain, because it would share every message from everyone using it. Add the person's exact address instead.
  • Your own team's domains and addresses are refused for the same reason: mail from inside the team is never shared with the team.
  • A domain or address already on another vendor is refused, and the message names the vendor that holds it.
  • A vendor cannot share a name with another live vendor. Removing a vendor frees its domain and its name for a different one, and leaves the threads it already brought in shared.
  • Adding a vendor also looks back. Every connected mailbox is searched, once, for the last 90 days of mail from the vendor's domains and addresses, and anything found joins the shared inbox. In someone's own mailbox, a thread that matches a vendor added after that mailbox was connected waits for its owner to confirm it, exactly like their first import; the team's shared address needs no confirmation. Adding fifty vendors in one spreadsheet still costs one search per mailbox.

Every add, edit and removal is written to the team's activity record with the person who made it and the vendor's state before and after. Its detail carries the vendor's name, owner, domains and addresses — never a message or a note.

Importing the list from a spreadsheet

Import a spreadsheet takes a pasted block of rows or a .csv file from the team's purchasing spreadsheet. Release 1 reads what you paste; reading a live Google Sheet from the cloud arrives later.

The import has three steps, and nothing is saved until the last one:

  1. Pick the columns. The importer guesses from the header row which column holds the vendor name and which holds its email addresses or domains, and you can change either. The owner column is optional; when it is there, each row's owner is matched to a teammate by email address.
  2. Preview. It shows every row it will add, every row it will add to a vendor that is already on the list, every row that changes nothing, and every row it cannot use with the reason — a free mail domain, a domain another vendor already holds, a blank name, a cell that is neither an address nor a domain, or an owner who is not on the team.
  3. Import. It writes the rows it showed you.

Running the same import again creates no duplicates. A row whose vendor name is already on the list is matched to that vendor by name; if the sheet brings a domain or address the vendor does not have yet it is added to that vendor, and if it brings nothing new the row is left alone. Two rows in one sheet with the same vendor name become one vendor with both sets of contacts. A default owner is only filled in when the vendor has none, so a re-import never reassigns work.

Every import finishes by recording one entry in the team's activity record with how many vendors it added, updated, left alone and refused.

Connecting mailboxes

A team brings mail in by connecting Google mailboxes. An admin connects the team's shared address (for example a supply address), and each member connects their own Gmail. The permission is a new Google grant held by the Supermail backend for the team. It is never the desktop's own Google connection and never the person's personal Supermail sign-in.

Connecting always goes through one page before Google's own consent screen. That page says, in plain words:

  • The team will see only threads with known vendors, or threads the person shares. Nothing else in the mailbox is shown to anyone.
  • Teammates can reply from this address on shared vendor threads, signed with their own name, and the reply appears in the mailbox's Sent folder. A tick box on the page turns that off, and the mailbox's owner (an admin, for the shared address) can switch it later.
  • Disconnecting stops new mail at once and erases the team's permission. Threads already shared stay with the team.
  • Which Omniscio account started the connect, so a forwarded link is easy to spot.

After Google, the page says the mailbox is connected. If a member already keeps that same address in Supermail through its own cloud sign-in, the page tells them so plainly: Supermail already holds that mail privately, and only vendor threads, plus threads they share, reach the team. The shared address, and every other new connection, reads headers first and fetches a message's text only when it matches a vendor.

When Google answers that the app is blocked by the company, the page names who must act: the company's Google Workspace administrator, who allows Supermail in the Google Admin console under Security, then API controls, using the app's client ID shown on the page. A person who cancels at Google, or unticks the mail permissions, ends up with nothing stored.

The shared address belongs to the team, not to the admin who connected it: another admin can reconnect it, and the threads stay with it. A personal mailbox can be reconnected only by its owner, and a reconnect must sign in to Google as that same address. Disconnecting (by the owner, or by an admin) erases the stored sign-in at once. It does not withdraw the grant at Google, because Google withdraws a whole sign-in at a time, which would also cut off the person's own Supermail mailbox and any other team using that address.

Every connect, reconnect, disconnect and change to the reply switch is written to the team's activity record.

The Mail Connections screen

Mail Connections in the Supermail navigation lists the mailboxes that feed the team and is where a mailbox is connected. The row appears only when the Shared Inbox is on for a workspace you belong to, beside Vendors.

Each mailbox shows its address, whether it is the team's shared address or whose own mailbox it is, and its health in words: Working, Needs reconnecting or Disconnected, with when it last checked in (or Not checked in yet). Quiet is healthy: a mailbox that has not checked in yet has simply had no poll since it was connected.

What a person can do on a row follows their role:

On the screen Member Admin
Connect the team's shared address Not offered Yes
Connect their own mailbox Yes Yes
Reconnect the shared address Not offered Yes
Reconnect their own mailbox Yes, when it needs reconnecting Yes
Switch Teammates may reply on the shared address Not offered Yes
Switch Teammates may reply on their own mailbox Yes Yes, until the owner changes it
Disconnect the shared address Not offered Yes
Disconnect their own mailbox Yes Yes

A member is shown one line in place of the shared-address button, in the backend's own words: Only a team admin can connect the team's shared address. The screen never offers an action the backend would refuse.

  • Connect sends the person to the Google permission page in their browser, where the plain-words page above explains what the team will see. When they come back, Check again re-reads the list; a connect finished in the browser does not update the screen on its own.
  • Reconnect runs the same way for a mailbox that needs it, and must be signed in at Google as that same address.
  • Disconnect asks once, in a plain confirm: new mail from that address stops reaching the team at once, and the threads already shared stay with the team.
  • Teammates may reply is the reply switch described above, set per mailbox. Only the mailbox's owner (or an admin, for the shared address) sees it.

How vendor mail comes in

A connected mailbox starts feeding the team the moment it is connected, and Gmail tells the backend about each new message within seconds. A check every few minutes catches anything a notice missed.

  • Addresses first. For each new message the backend reads only who it is from, who it went to, and the reply ids that say which earlier email it answers. It never asks for the subject or the preview line at this point, and keeps none of it for mail that is not shared.
  • Text only for vendor mail. When an address belongs to a vendor on the list, the backend fetches the whole message and files it for the team. Any other message is never opened further, and nothing about it is stored.
  • Mail a machine sent starts Done. A receipt, a shipping notice, a newsletter or an out-of-office reply is shared and readable like any other message, but the conversation it opens starts Done, it never moves a conversation, and it never starts the follow-up clock. Whoever works the thread can still set it to Needs reply. The backend reads this from the message's own headers and never from its text: Auto-Submitted with any value but no, a bulk, junk or list Precedence, a List-Id or List-Unsubscribe, an auto-reply header, a no-reply sender such as no-reply@, or an automatic-reply subject such as "Automatic reply:" or "Out of office".
  • Later mail on a shared thread. A reply on a thread the team already has joins it when it comes from a vendor or from someone already on that conversation. A message the person sends on that thread joins only when it goes to someone already on the conversation or to a vendor, so a private forward stays private.
  • Never drafts, spam or trash. Those are skipped before anything is read, and so is a thread someone has marked as personal.
  • A record that proves it. Every read is logged as "addresses only" or "whole message", with whether it matched a vendor, and never with an address or a subject.
  • Deleting in Gmail does not delete for the team. A message already shared stays shared.
  • Same mail, once. The same notice arriving twice, or a message seen through two connected mailboxes, is stored once.
  • One email, one copy. A vendor email that reaches three buyers and the shared address is stored once, with all four mailboxes listed as where it came from.
  • Replies follow the email they answer. A reply joins the conversation of the email it answers, found by the email's own reply ids rather than its subject. So a reply from a vendor's freight forwarder joins even when it reaches a buyer who was not on the first email, or comes under a new subject. Two separate emails with the same subject stay two conversations.
  • Our own replies are not doubled. Gmail gives every sent email a new id. A reply the team sends is recognised by its own send record and shown once.
  • Split and join. Any member can split messages that were wrongly put together into a conversation of their own, or join two conversations that belong together. Both show in the conversation's history, and either can be undone by the opposite move. A conversation emptied by a join is closed.
  • Replies sent from Gmail itself count. A reply the person writes and sends in Gmail, even one that sat as a draft first, joins the conversation under the same rule as any message they send.
  • A permission Google stops accepting. If the person withdraws the permission at Google, or an administrator blocks it, the mailbox shows as needing a reconnect and nothing more is read from it until someone reconnects it.

A mailbox that also uses Supermail's own cloud sign-in is read the same way, through the team's own permission, so the team never reads anything from that person's private Supermail store.

The first 90 days

Connecting a mailbox brings in the last 90 days of vendor mail for that address, so the Shared section opens with real work in it instead of an empty list. The import searches Gmail for the team's vendor addresses and domains in both directions — what the vendor sent us and what we sent to them — so mail from anyone else is never even listed, let alone opened.

While it runs, the mailbox's row shows how far it has got: how many conversations it has brought in so far. That count and the import's own place are held on the backend, so the screen can be closed, or the backend restarted partway through, and the import picks up where it stopped instead of starting over.

Each imported conversation starts in the state that matches where the thread left off:

  • Waiting on vendor when the last message a person sent or received on it came from us.
  • Needs reply when the vendor wrote within the last 14 days. It goes to that vendor's default owner.
  • Done when the vendor's last message is older than that, and for a thread whose only mail was sent by a machine. It can still be read and searched, and it moves back to Needs reply the moment the vendor writes again.

Mail a machine sent never decides a thread's state here, exactly as it never moves one elsewhere: a shipping notice that lands last does not make a vendor's question look quiet. The 14-day rule is what keeps the first morning from being 90 days of backlog — only the threads someone still has to act on arrive as open work.

Your mailbox's first share waits for you

When you connect your own Gmail, nothing from it reaches your teammates until you have looked at it once. The team's shared address skips this step.

  • Only you see the first batch. The 90 days of vendor mail the import brings in, and any new vendor thread that arrives before you confirm, wait in a review under your mailbox on Mail Connections. Teammates see none of it: no thread, no count, no activity entry, no alert. A teammate who asks for one is told it was not found.
  • Check it, then share it once. The review lists every waiting thread with its vendor, date and message count. Press This is personal on any thread you do not want the team to have: it is deleted from the team's copy and is never brought in again. Then press Share N threads. Your teammates see them at once, and from then on vendor mail from your mailbox is shared as it arrives.
  • Replies on a waiting thread wait too. New mail on a thread that is waiting joins it in the review.
  • While the import runs, Share waits. The review says it is still bringing in your mail and checks again by itself. If the import stops because the mailbox needs reconnecting, reconnect it to finish, then share.
  • Mail the team already has stays with the team. If the same email also reached the shared address, the team sees the shared address's copy as usual. Your own copy, and anything only you received on that thread, still waits for your review, and joins the team's conversation when you press Share. A thread that is partly with the team already cannot be kept personal from the review.
  • A vendor added later waits once. When someone adds a vendor after your mailbox connected, its first matches in your mailbox wait in the same review. Once you share that vendor's threads, later mail from that vendor is shared at once; a vendor whose threads you kept personal keeps waiting for you.
  • Sharing a waiting thread by hand is refused with a pointer to the review, so one Share decides it.

Sharing a thread by hand

The vendor list will miss a thread now and then — a new supplier, a person writing from a personal address. On any thread in your own Supermail view, Share with team files the whole thread for the team in one click.

  • The action appears only on a mailbox you own that feeds a team, in every personal mail mode. Sharing from somebody else's mailbox is refused, whoever asks; on the team's shared address it is an admin action, the same rule that governs connecting it.
  • The backend fetches the thread through the team's own mailbox permission, so a thread whose sender is not on the vendor list still reaches the team with its full text.
  • Drafts, spam and trashed messages in the thread are skipped, exactly as in the automatic path, and nothing about them is stored.
  • The team's activity record names the person who shared it, and the conversation remembers it came in by hand rather than by matching a vendor.
  • Sharing a thread the team already has adds any message it was missing and records who shared it again; it never creates a second copy of a message or a second conversation.
  • Mail a machine sent is filed the same way it is everywhere else: the conversation it opens starts Done and never starts the clock.

Attachments

Files on shared vendor mail belong to the team, not to the mailbox they arrived in.

  • Kept when the mail is shared. When a vendor message is shared, its attachments are copied into the team's own storage on the Supermail backend, so an invoice or a packing list still opens after the teammate who received it disconnects their mailbox or leaves.
  • Up to 25 MB each. A larger file is listed with the message but is not copied. It opens straight from Gmail while the mailbox it came through is still connected, and stops opening once that mailbox is gone.
  • Only your team. Only members of the team can open its files. Anyone else, including a member of another team, is told the file does not exist. A file on a conversation still waiting for its owner's first-share confirmation opens only for that owner.
  • A copy that fails is tried again. If Gmail is busy or the backend restarts mid-copy, the next check of that mailbox tries the file again, newest files first.
  • Files attached to a reply will be stored the same way once replying from the Shared section arrives; the storage half is in place now.
  • Nothing changes in Gmail. Reading a file never moves, labels or deletes anything in the mailbox.

"This is personal"

A vendor match can catch a personal email now and then — a friend who works at a supplier, a personal purchase from a vendor's shop. The owner of the mailbox it came through can take it back out of the Shared Inbox for good.

  • Only the mailbox's owner can do it. A teammate asking is told the conversation was not found. A thread that also reached the team through the shared address or another person's mailbox cannot be removed this way, because the team has its own copy.
  • It hides at once, with a short undo. The thread leaves the team's view the moment it is marked, and the owner gets an undo for the team's undo window (10 seconds unless an admin changed it). A reply that arrives during that window is kept, so an undo brings back the whole thread.
  • Then it is gone for good. When the window ends, the thread, its team notes, its Agreed Terms and any reply still waiting to go out on it are deleted from the cloud copy. It skips Trash. The real mailboxes are untouched. The team's activity record keeps only that a thread was removed as personal, with how many notes and teammate replies it had, never its words or its sender.
  • It is never shared again by itself. New mail on that thread is not brought in, by the automatic path, the 90-day import or a vendor re-check. Only the owner sharing it again by hand brings it back.
  • The sender is remembered as personal. Each person who wrote on the thread is remembered by their exact address, never their whole domain, for that mailbox. A new thread from or to that address is not shared, while other people at the same vendor still are.
  • The owner sees the list and can change it. Under the person's own mailbox on Mail Connections, Remembered personal senders lists every remembered address with a Remove button. Nobody else can see this list.
  • What was shared from your mailbox. The same place shows what was shared from that mailbox in the last day, and every reply a teammate sent from that address, with who it went to. A daily in-app alert carrying this list arrives with the team alerts.
  • If the removal cannot finish. A removal is finished by a background step; if that step is interrupted, the regular mailbox check picks it up again within a few minutes, so a marked thread never stays hidden but stored.

The Shared section

Shared in the Supermail navigation is where the team reads its vendor mail. The row appears only for a person who belongs to a workspace whose Shared Inbox is on; everyone else has no such row, and the backend answers "not found" to every shared request they make.

  • Every shared conversation, one list. Each row shows the subject, the vendor, how long ago it last moved and its state. A conversation with no messages is never listed.
  • Browse by vendor or by mailbox. One picker narrows the list to a single vendor, a second to the conversations that reached the team through one mailbox (the shared address or a teammate's), and a third to a state. They combine, and clearing them brings the whole list back.
  • Search by vendor, person or a word in the body. A vendor's name finds its conversations, an address or a person's name finds a conversation that person wrote on, and a word finds it inside the message bodies. Results replace the list until the search is cleared. A search never reaches outside the team and never returns a thread that is hidden from the person searching.
  • A thread, read-only. Opening a conversation shows every message in order with its sender, its recipients, its words and the names and sizes of its files, plus the addresses on the thread, its vendor and its state. Nothing on this screen changes a conversation: replying, notes, changing state or owner arrive in later steps.
  • A thread waiting for its owner. A thread held for the first-share confirmation shows only to the mailbox's owner; teammates do not see it, count it or find it in a search.
  • "This is personal" on the thread. Where a thread reached the team only through the person's own mailbox, the thread carries This is personal. It asks once, hides the thread from the team at once, and shows an Undo counting down the team's undo window. When the window closes the removal is final and the thread is deleted from the cloud copy, exactly as described above.

What it does not do yet

Reading is what the Shared section does now: every shared conversation, browsed by vendor and by mailbox, searched, and opened with its messages and its file list. Sending a reply, team notes, changing a conversation's state or owner, the Morning View and the phone version arrive in later steps of the same build, and vendor mail is already being filed for them. Files are listed on a message; a download straight from the thread arrives with the reply composer. If the first email of a thread reaches the team only after its replies already came in through another mailbox, it starts its own conversation, and a member can join the two.

Last verified 2026-11-21