Set Up a Shared Inbox for a Team on Google Workspace
Learn how to turn a Google Group into a functional shared inbox for your support team, including permissions, delegation, and testing, plus when a purpose-built tool saves time.
On this page
- Step 1: Verify Google Workspace Plan and Admin Access
- Step 2: Create a Group for the Shared Inbox
- Step 3: Configure Group Settings for Email Delivery
- Step 4: Add Team Members to the Group
- Step 5: Set Up Delegated Access (Optional but Recommended)
- Step 6: Test the Shared Inbox
- Common Mistakes to Avoid
- When a Dedicated Shared Inbox Tool Makes Sense
You'll finish this guide with a working shared inbox that lets multiple teammates read, reply to, and track emails sent to a single address like support@yourdomain.com. Before you start, you need a Google Workspace account with admin privileges and a list of the team members who will use the inbox.
Step 1: Verify Google Workspace Plan and Admin Access
Sign in to the Google Admin console with a super admin or groups admin role. Confirm your Workspace plan includes Groups for Business, it's included in Business Standard, Business Plus, Enterprise, and Education editions. If you're on Business Starter, you can still create groups but some advanced settings (like collaborative inbox features) are limited. Knowing your plan early avoids hitting a wall later when you try to enable features that aren't available.
Step 2: Create a Group for the Shared Inbox
In the Google Admin console, create a new group (see Google's help documentation for the current steps).
- Name: Choose a clear name like "Support Team".
- Email address: Use a functional address such as support@yourdomain.com.
- Description: Add a short note for future admins (e.g., "Shared inbox for customer support emails").
- Group owners: Add at least one other admin as co-owner so the group isn't orphaned if you leave. Click Next, then Create group. Wait a few minutes for the group to propagate across Google's systems before moving on.
Step 3: Configure Group Settings for Email Delivery
Open the group's settings in the Admin console (refer to Google's help docs for the exact navigation) and adjust these key settings:
- Who can post: Set to "Anyone on the web" so external customers can email the address.
- Who can view conversations: Set to "All members of the group" so every teammate sees the full thread.
- Who can join: Keep as "Only invited users" to maintain control.
- Allow external members: Turn off unless you deliberately want non-Google accounts added as members.
In the group's email options (see Google's help docs), set:
- Email footer: Add a standard footer (e.g., "This email was sent to support@yourdomain.com").
- Replies: Choose "Reply to group" so replies stay in the shared thread.
- Conversation history: Enable "On" so new members see past emails.
These settings determine whether the group behaves like a true shared inbox or just a distribution list. The "Reply to group" option is critical, without it replies go only to the sender and break the shared view.
Step 4: Add Team Members to the Group
Add members to the group using the Admin console (see Google's help docs). Enter each teammate's Workspace email address. Assign the Member role (not Manager or Owner) unless they need admin rights over the group. After adding everyone, send a quick internal note so they know the inbox is live and where to find it in Gmail (under Groups in the left sidebar).
Step 5: Set Up Delegated Access (Optional but Recommended)
Enable mailbox delegation for your domain in the Admin console (see Google's help documentation). Then each team member (or an admin on their behalf) can grant access to the shared inbox from their Gmail settings (see Google's help docs for the current steps). The shared inbox will send a confirmation email; accept it. Once confirmed, the shared inbox appears as a separate tab in each teammate's Gmail, letting them triage, reply, and archive without leaving their personal inbox.
Step 6: Test the Shared Inbox
Send a test email from an external address (e.g., a personal Gmail account) to support@yourdomain.com. Verify:
- The email appears in the group's conversation view.
- All members receive it in their Groups sidebar (and in their delegated tab if set up).
- A reply from a teammate shows "sent from support@yourdomain.com" and stays threaded in the group.
- Archiving or labeling works as expected.
If anything fails, re-check the group's posting permissions and delegation confirmations. Common issue: the test email bounces because "Who can post" is still set to "Group members only."
Common Mistakes to Avoid
- Using a distribution list instead of a Group: Distribution lists forward copies; they don't provide a shared conversation view or delegation.
- Forgetting "Reply to group": Replies go to the individual sender, fragmenting the thread.
- Adding members as Managers/Owners unnecessarily: Increases risk of accidental setting changes.
- Skipping delegation: Teammates must constantly switch to the Groups interface, slowing response times.
- Not testing with an external address: Internal tests always work; external delivery is what matters.
- Ignoring conversation history for new hires: Enable it so onboarding doesn't mean starting from zero.
When a Dedicated Shared Inbox Tool Makes Sense
Google Groups works for basic shared inboxes, but it lacks ticket status tracking, collision detection (two people replying at once), AI reply suggestions, and automated assignment. If your team is handling more than a few dozen emails a day, or you need clear ownership and reporting, a purpose-built tool eliminates the workarounds. NeuraDesk includes a shared inbox, AI reply suggestions, ticket status tracking, and automatic email-to-ticket conversion, all free to start with no per-agent fees. try NeuraDesk free
Join teams already using NeuraDesk
Ready to get started?
Create your workspace and try NeuraDesk for free.
Sign up free