Google Workspace is the default choice for most founders who want professional email. It's reliable, widely compatible, and integrates with everything. At six dollars per user per month for the basic tier, it's not expensive. Most people who've built a company in the last decade have at least one Workspace organization.
If you have more than one company, you probably have more than one Workspace organization. And that's where it gets complicated.
This post is specifically about how to run email cleanly across multiple Google Workspace accounts: which inboxes to connect, what to centralize versus what to keep separate, and which tools actually make the multi-company setup work.
Google doesn't have a native way to manage multiple Workspace organizations from a single dashboard. Within one organization, you can have many users and aliases. But across organizations, you're switching accounts, which means switching browser profiles, re-authenticating constantly, or using an email client that handles multiple accounts.
The typical workaround is email delegation or forwarding. You designate one account as your main inbox and forward everything else there. This gets all your mail into one place but brings back the identity problem: when you reply from the aggregated inbox, your reply may go from the wrong account unless you've been meticulous about setting up the send-as configuration.
A more robust approach is connecting each Workspace account directly to an email client or dashboard that treats each organization as its own context, so you see all your businesses at once without merging them into a single confusing stream.
Before thinking about how to aggregate across accounts, get each organization set up properly.
Workspace IMAP access is sometimes disabled by administrators, which blocks external email clients from connecting. In your Workspace admin console under Apps, Gmail, and then End User Access, confirm that IMAP is enabled for your organization. If you're the admin, this takes thirty seconds.
Google's standard authentication flow requires an App Password for email clients that use IMAP directly rather than OAuth. You create App Passwords in your Google Account settings under Security. You'll need two-factor authentication enabled first, which you should have anyway.
Create a named App Password for each account you're connecting. Name it after the client you're using so you can revoke individual ones later if needed. This is a sixteen-character password you'll paste into your email client once and won't need to manage after that.
Within each Workspace organization, set up send-as aliases for any secondary address you want to send from. If your agency uses hello@, support@, and billing@ at the same domain, configure all three as send-as aliases in the primary account's Gmail settings. This lets you send from any of them without needing separate accounts.
The send-as setup is in Gmail Settings under Accounts, then Send mail as. Add each alias, verify it, and set a custom reply-to address if needed. This takes about five minutes per alias.
This is the step most people skip and then regret. Write a proper signature for each email address you'll be sending from, including any aliases. Include the business name, your title, a contact method, and your website. Keep each one short.
The reason to do this before you set up any dashboard or aggregation is that it forces you to think explicitly about which identity goes with which address. That clarity is what you need to configure the rest of the setup correctly.
Once each account is configured correctly, you need something to show them all in one place while keeping them separate.
Using multiple browser profiles in Chrome is the officially supported approach for managing multiple Google accounts, but it's awkward. You're switching between windows that look identical except for which account is active. There's no overview of all your inboxes. You have to navigate to each one separately to see what's there.
Gmail's built-in account switching, where you use the avatar in the top right to switch between signed-in accounts, is even less suited to this. It switches your entire Gmail view between accounts, so you're seeing one business at a time and have no peripheral awareness of what's happening in the others.
An IMAP email client that connects to all your accounts simultaneously and shows them in a way that respects their separate contexts. This is where desktop clients like Thunderbird, Spark, or Canary have an advantage over web-based Gmail: they can maintain connections to multiple accounts and display them in a single interface without requiring you to switch views.
The limitation of most of these clients is that they still treat accounts as the organizing unit rather than businesses. If you have two Workspace accounts for the same company, two different aliases at one account, and a separate personal account, they all appear as equal entries in the sidebar.
What the multi-company founder actually needs is a layer above accounts. The Agency is a business. That business might have one Workspace account with three aliases, and they all belong in the same context. The SaaS is a different business with its own account and maybe a shared support@ alias. You want to see Agency on one side of the screen and SaaS on the other, not a list of four email addresses sorted by account.
Cereal is built around this model. You configure each account and then assign it to a business bowl. The dashboard shows you bowls, not accounts. All the Agency email is in the Agency bowl, regardless of which specific address or alias it came to. When you compose from the Agency bowl, your identity defaults to the Agency's primary address.
Even with a clean setup, some email will arrive at the wrong place. A contact will use your personal Gmail when they should have used your business address. Something you signed up for with a Workspace address will start routing to the wrong organization.
The right approach is to fix the routing at the source rather than merging everything and dealing with it downstream.
For contacts who use the wrong address: reply from the correct one and ask them to update their records. Most people do this once and then use the right address forever. The reply-from header will usually prompt email clients to update their suggested addresses automatically.
For service accounts that have the wrong address: update your email in those services to the correct one. This is tedious but one-time work. A quick search for your current email in each of your accounts will surface most of them.
If you're starting fresh, here's the order of operations:
Multiple Workspace organizations means multiple billing relationships with Google. At six dollars per user per month, three organizations with one account each is eighteen dollars per month. That's not unreasonable for what you get, but it's worth knowing that Workspace charges are per organization, not per account across organizations.
If cost is a concern, some of your secondary businesses may not need Workspace. Providers like Fastmail, Zoho, or even your domain registrar's mail hosting can work fine for businesses where you're the only user and your requirements are simple. These providers support IMAP and can be connected to the same dashboard alongside your Workspace accounts. The dashboard sees IMAP accounts, not Workspace organizations, so mixing providers is straightforward.
Getting this right takes an afternoon. After that, it mostly runs itself. Each business has its own email identity, each account connects to a dashboard that keeps the businesses separated, and you can see what's happening across all of them without switching contexts or maintaining multiple browser windows.
The thing worth emphasizing is that the goal is not just to receive all your email in one place. Plenty of forwarding setups achieve that. The goal is to receive all your email in one place while maintaining the separation that lets you operate as a professional in each business independently. Those are different requirements, and only the second one is worth building toward.