Google Workspace accounts connect the same way personal Gmail accounts do, through OAuth, but there are a couple of extra steps if your organization restricts third-party apps. Here is the full path from zero to a synced inbox.
Before you start
- Confirm you are on a Mac with Apple Silicon running macOS 15.1 or later. STAMP does not run on Intel Macs or older macOS versions.
- Know your Workspace login (your work email and password, plus two-factor if your org requires it).
- If you are not the Workspace admin, check whether your organization restricts third-party app access. If it does, you will need five minutes of an admin's time partway through.
Step-by-step setup
- Download and open STAMP. Launch the app and click "Add Account."
- Choose Google. STAMP treats Workspace and personal Gmail the same way at this step, both use Google's OAuth flow.
- Sign in with your Workspace email. You will land on Google's own sign-in page, not a STAMP-branded one. This is deliberate: your password is typed directly into Google, never into STAMP.
- Read the consent screen. Google shows you exactly what STAMP is asking permission for before anything connects. You will see requests for:
- Read, send, and manage your mail. This is the core permission. Without it, STAMP cannot show your inbox or let you reply.
- Manage your mail labels. Needed so STAMP can apply and read labels the same way Gmail's own interface does.
- View your basic profile info (name, email address, profile photo). Used to show your account correctly in the sidebar and compose window, nothing more.
- Approve the consent screen. If your organization has not restricted third-party apps, this completes immediately.
- If you see "This app is blocked" or "Verify with your admin," your Workspace admin has third-party app access locked down. Send them the app name and ask them to approve it in the Google Admin console under Security → API Controls → App Access Control. This is a five-minute task on their end.
- Wait for the initial sync. STAMP pulls your existing folders (from Gmail labels) and recent mail first, so your inbox is usable within a minute or two even on a large mailbox.
- Add any send-as aliases. If your Workspace account sends from more than one address, add each alias in STAMP's account settings so replies go out from the correct one.
- Repeat for additional accounts. If you also have a personal Gmail, Outlook, or iCloud account, add those the same way. STAMP unifies all of them into one view.
Why OAuth instead of a password field
STAMP never asks for your Workspace password directly. Every Google account connects through OAuth, which means:
- Your password stays with Google, always.
- The permission you grant is scoped and visible, you saw exactly what was requested in step 4.
- You can revoke access at any time from your Google Account's connected apps list, no need to change your password.
This matters more for Workspace accounts than personal ones, since a compromised work account can expose client data, financial records, or a whole team's correspondence. OAuth keeps that risk contained to a revocable token, not a password an app could mishandle.
What happens if a provider doesn't support OAuth
Google, Outlook, and Microsoft 365 all support OAuth, and STAMP uses it by default for each. Providers that don't (some custom IMAP setups, Proton Bridge) use an app-specific password instead, generated in that provider's own settings and typed once into STAMP. Either way, your primary account password never touches STAMP's servers.
After you're connected
Once your Workspace account is syncing, the fastest way to get comfortable is learning the four core shortcuts: J and K to move between messages, R to reply, E to mark done. Add S for snooze once those feel automatic. Full list and rationale in our shortcuts guide.
Check the changelog periodically. Workspace-specific improvements, like shared mailbox support, tend to land there first.
Built for teams that live in Workspace. hello@stamp.email