This page is for the person at exactly that point: past the shared login, not sure whether to reach for Gmail delegation, a Google Group, or a proper tool. Here’s what each one actually does, where each runs out of road, and what changes when you move to a real shared inbox.
The three things Gmail people confuse
They sound alike, and Google’s own naming doesn’t help. But a shared Gmail account, Gmail delegation, and a true shared inbox are three different setups.
A shared Gmail account is one mailbox with the password handed round. Everyone logs into the same inbox as the same person. It’s free and it’s instant, which is why almost everyone starts here. It’s also the one that breaks first.
Gmail delegation lets you grant other Google accounts access to your mailbox, so a colleague can read and send from it under their own login — Google caps it at 25 delegates. Better than a shared password, because you can see who’s who. But delegation was built for an assistant handling an executive’s mail, not for a team fielding customer conversations together.
A Google Group, set up as a collaborative inbox, turns an address into a distribution list where members can assign and resolve conversations. Closer in spirit to what you want — but it’s a bare-bones feature buried in Google Workspace admin, with no customer context, no mobile experience worth the name, and none of the channels a small brand actually lives on now.
A true shared inbox is a separate tool that connects to your existing address and gives the whole team one view — who’s replying, what’s still waiting, the full history with each customer — without anyone impersonating anyone. That’s the category Vidual Inbox sits in, built for teams of one to ten who’ve outgrown the login but don’t want an enterprise help desk.
| Setup | Built for | Where it runs out |
|---|---|---|
| Shared Gmail account | Two people, day one | No assignment, no ownership, one password for everyone — breaks at three or four people |
| Gmail delegation | An assistant handling one person’s mail | Separate logins, but still no assignment, status, or team view; capped at 25 delegates |
| Google Group (collaborative inbox) | Internal lists, basic triage | Buried in Workspace admin; no customer context, weak on mobile, email only |
| True shared inbox | A team answering customers together | Only if you need help-desk machinery — SLAs, tiers, automation — at real volume |
What breaks when a small team shares one Gmail login
Nothing crashes and the bill doesn’t go up. The setup just stops holding, usually right when you’re busiest.
- No idea who replied. Two people open the same email and both answer it — or both assume the other has, and the customer hears nothing. The only way to check is a dig through the sent folder, if the reply even went out from the shared account and not someone’s personal one.
- No assignment. There’s no way to say “this one’s mine.” Ownership lives in people’s heads, and follow-ups sit because they were nobody’s job.
- No history that follows the customer. A repeat customer’s emails and their Instagram DMs arrive as unrelated threads from unrelated strangers. Nobody sees they’re the same person, let alone a regular.
- The password problem. Someone leaves, and you’re resetting the password and re-telling everyone. Two-factor authentication on a shared login is a small nightmare. Security and simple handover pull in opposite directions.
- Only one channel. The email might be shared, but the Instagram DMs live on one person’s phone and the website chat pings whoever’s at the desk. Nothing joins up.
Every one of those is a symptom of the same thing: the login is shared but the work isn’t. If you want to test how far your own setup has drifted, the ten questions in what email collaboration actually means take about a minute to answer.
None of this means the team is disorganised. As we put it in the launch piece: the setup isn’t broken — it’s held together with memory and good intentions. It just doesn’t scale past a couple of people.
Coming from Gmail: what you keep, what you lose, what you gain
The fear, understandably, is that moving to a dedicated tool means abandoning Gmail, migrating years of email, and teaching everyone something new. It doesn’t.
You keep your address. Customers still email hello@ or info@. Replies still go out from that address, with your signature. The customer never sees “Vidual” — to them, nothing changed.
You lose the things you were fed up with. The shared password, the “did anyone answer this?”, the guessing about who owns what.
You gain one room the whole team works in. Every conversation — email, Instagram DM, WhatsApp, live chat — arrives in the same stream, with a name on it and a status you can read at a glance. The question that haunts a shared login — did anyone reply to this? — stops being a question, because you can see it’s handled, and by whom. Internal notes let the team talk to each other right beside the customer’s message instead of forwarding threads around. And the history follows the person, not the channel, so whoever picks up a conversation picks up the whole relationship.
That changes the texture of the day more than the toolkit. Mornings start with one glance down the list — what’s waiting, what’s mine — instead of a re-read of the whole inbox to be sure. A handover is a note, not a forwarded thread with “can you take this?” in the subject line. And when someone’s away, nothing they were holding goes invisible.
What you don’t gain — deliberately — is the machinery of a help desk. No ticket numbers, no SLA timers, no automation rules. If you need those, Freshdesk or Zendesk are the better call, and we’ll say so. If you’ve been putting off the switch because every tool you found felt like a call centre, that’s the gap Vidual Inbox was built for. Our shared inbox or help desk decision tree walks through which side of that line you’re on.
How connecting an existing Gmail actually works
This is the part Gmail users worry about most, and it’s the part we made easiest. There’s no migration and no exporting years of mail.
You forward your shared address to the unique Inbox address you get on signup — on Gmail that’s one popup and one forward, with no DNS records to wrangle. From then on, every email that arrives becomes a conversation the whole team can see, assign and reply to.
For sending, you can authorise your Gmail so replies go out through your own address and land in your Gmail Sent folder. Worth being precise about the permissions, because it matters: we request only the gmail.send scope. We do not read your incoming mail, your Sent folder, your drafts, or any other Gmail content. The token is encrypted at rest, and you can disconnect any time from the Integrations page — or revoke it yourself at myaccount.google.com/permissions. The whole setup — forward, connect, invite the team — fits comfortably inside an afternoon. The how it works section on the homepage has the step-by-step.
Common questions
What’s the difference between a shared Gmail account, Gmail delegation, and a true shared inbox?
A shared Gmail account is one mailbox everyone logs into with the same password. Gmail delegation lets other Google accounts access a mailbox under their own login — built for an assistant handling one person’s mail, capped at 25 delegates. A true shared inbox is a separate tool that connects to your address and gives the whole team one view — assignment, internal notes, customer history — without anyone sharing a password or impersonating anyone.
What breaks when a small team shares one Gmail login?
The predictable things: nobody knows who replied, so emails get answered twice or not at all; there’s no way to assign a conversation, so follow-ups slip; there’s no customer history tying a repeat customer’s emails and DMs together; and every time someone leaves, you’re resetting the password for the whole team. It works for two people and starts failing at three or four.
How does Vidual Inbox connect to an existing Gmail address without migrating email?
You forward your shared Gmail address to the Inbox address you’re given on signup — one popup and one forward, no DNS. Incoming mail becomes shared conversations from that point on; nothing is migrated or exported. To send from your own address, you authorise Gmail under the single gmail.send scope, so replies land in your Gmail Sent folder. We never read your incoming mail.
What do you lose or gain moving from Gmail to a dedicated shared inbox tool?
You keep your address and your brand-facing replies. You lose the shared password, the duplicate replies, and the guesswork over who owns what. You gain a team-wide view, assignment, internal notes, a “still waiting” filter, and one customer record across email, Instagram, WhatsApp and chat. What you deliberately don’t get is help-desk machinery — ticket numbers, SLAs, automation — the right trade for a team of one to ten and the wrong one for a fifty-person support floor.
If a shared Gmail is starting to cost you replies, the fix keeps your address and your Gmail — and puts the whole team in one room, seeing the same conversations. Vidual Inbox is a 14-day free trial, no card needed. £24.99/month after that, unlimited team, no per-seat charges. Or book a 20-minute call and we’ll walk through your Gmail setup together — including the bits where we’d point you somewhere else.