To secure Google Workspace in a small company, enforce 2-Step Verification for everyone, keep super admin to two people who don't use it for daily work, review which third-party apps can read your users' data, set Drive sharing to warn before anything leaves the company, and lock leavers out properly. Google's help pages put no edition limit on any of the five, so this Google Workspace security baseline applies from Business Starter up.
Every setting below comes from Google's own Workspace Admin Help pages as we read them on 27 October 2026, linked so you can check the current wording. For each one we note the editions Google's page says it needs. Where a page names no edition limit, we say so. Admin console menus move occasionally, so if a path differs slightly, search the help page title.
Why Google Workspace comes first
In most small companies, the Google account is the key to everything else. People "Sign in with Google" to half their tools, password resets for the other half land in Gmail, and your files live in Drive. A compromised Google account is a compromised company. Securing it is the highest-leverage hour you will spend on security this year, and it is the first step in any wider SaaS security plan.
Google publishes its own security checklist for small businesses (1–100 users). It is short and sensible. This post follows the same priorities, adds third-party apps and leavers, and gives you the exact settings.
2-Step Verification
2-Step Verification (2SV) is Google's name for multi-factor authentication: a sign-in needs a second proof besides the password. The settings live at Admin console > Security > Authentication > 2-step verification, and you need to be a super admin. Google's deployment guide names no edition limit for any of the steps below.
Let people enroll before you enforce. Tick Allow users to turn on 2-Step Verification, leave enforcement off, and tell people to enroll. Nobody gets locked out while they set up their phones and keys.
Track enrollment. The report under Reporting > User Reports > Security shows who has enrolled, so you know whom to chase before the deadline.
Turn on enforcement. Set Enforcement to on, either now or from a date. Google notes enforcement may start within 24 to 48 hours of the date you pick. You can apply it to an organizational unit or a group, so enforce for admins first, then everyone.
Give new hires an enrollment period. The New user enrollment period runs from 1 day to 6 months. A week is plenty for most small companies; six months is a long window for an account with no second factor.
Choose the allowed methods. The options are any method, any except text and phone codes, or only security keys. If you restrict methods, read Google's warning first: people who only use text or phone codes will be locked out when you switch those off.
Should you enforce it? Yes, for everyone. Google's own 2SV overview recommends enforcing it for admins and key users at minimum, calls security keys the most secure form of 2SV, and says Google is enforcing 2SV for administrator accounts. If you are weighing 2SV against single sign-on, SSO vs MFA explains why they solve different problems.
Admin accounts and roles
You assign roles from Directory > Users, on the user's page under Admin roles and privileges (assigning admin roles). The advice below follows Google's best practices for administrator accounts. Neither page names an edition limit.
Have two super admins, each with their own account. More than one super admin, each managed by a separate person, means losing one account does not lock you out. Who should be a super admin? Usually the founder or operations lead plus one trusted backup, and nobody else.
Keep super admin out of daily work. Don't use a super admin account for everyday activities, and don't stay signed in to it. Use an ordinary account day to day and sign in as super admin only when a task needs it.
Put security keys on admin accounts. Google recommends them for admins, with a spare key enrolled so a lost key is not a lost account.
Never share an admin account. A shared admin login makes the admin log useless, because it can't show who did what. The same logic applies to shared accounts everywhere else.
Add recovery details and keep backup codes. Give every admin account a recovery phone and email at Directory > Users > the user > Security > Recovery information (adding recovery information; no edition limit stated). Google's small business checklist also asks admins to print backup codes and store them somewhere safe.
Decide whether super admins can recover their own password. The setting is at Security > Authentication > Account recovery, under super admin account recovery (super admin recovery page). With it off, a super admin who forgets their password must ask another super admin or Google Support; Google recommends that when you have multiple super admins who can help each other. Google's page says the setting is off by default on Frontline Standard, Business Plus, Education Standard and Education Plus, Enterprise Essentials Plus, G Suite Basic and Cloud Identity Premium, and on by default for all other editions. With two super admins in place, turning it off removes a password-reset path an attacker could aim at.
Give everyone else a narrower role. Google's prebuilt administrator roles include User Management Admin (creates and manages non-admin users), Help Desk Admin (resets passwords for non-admin users), Groups Admin and Services Admin, and you can create custom roles. The person who adds new hires does not need super admin; the principle of least privilege explains the reasoning. The roles page names no general edition limit.
Require a second admin for sensitive changes, if your edition has it. With multi-party approval, a second admin must approve sensitive changes, such as turning 2SV off. Google's multi-party approval page lists it for Enterprise Standard and Enterprise Plus, Education Standard and Education Plus, and Enterprise Essentials Plus, and the Multi-party approval Admin role needs one of those editions. Business editions can skip this line.
Third-party app access
How do I see which apps have access? Admin console > Security > Access and data control > API controls, then Manage Third-Party App Access. The Accessed apps list shows each app your users have authorized with their Google accounts, how many users, and which Google services it requests, per Google's API controls page. The list updates 48 hours after access is granted or revoked. Google's page names no edition limit for these controls.
Sort by risk. Apps requesting Gmail or Drive come first. An app with one user and access to someone's whole mailbox deserves a closer look than a calendar widget used by twenty people.
Trust, limit or block. Configure the apps you rely on as Trusted or Limited, and set apps you do not want to Blocked.
Decide what happens with apps you have not reviewed. Under Settings > Unconfigured third-party apps, the options include allowing users to access only apps that ask for Google sign-in info, or not allowing third-party apps at all. The first is a good middle ground: people can still use "Sign in with Google", but a new app cannot read mail or files until you trust it. Google notes that the sign-in-only option is not available in Education editions, and that Education editions word the "don't allow" option differently.
This is also the best single list of shadow IT in a Google company. And if you use Google as the login for your other tools, the same list shows which of them people reach that way; Google Workspace SSO covers that setup.
Drive and Calendar sharing
Drive sharing lives at Admin console > Apps > Google Workspace > Drive and Docs > Sharing settings > Sharing options. You need the Drive and Docs admin privilege, and settings apply per organizational unit or group. Per Google's external sharing page, external sharing settings are supported on all Google Workspace, Cloud Identity and G Suite editions.
Warn before anything leaves the company. You can set sharing outside your organization to Off, Allowlisted domains only, or On, and with it on, choose to warn people before they share outside the company. Google's small business checklist recommends the warning.
Make new files private by default. The same checklist recommends changing the default for link sharing so new files are visible only to their creator until they share them.
Limit external sharing to specific folders, if you need it. Allowing only content in specific folders to be shared externally lists Business Starter, Business Standard and Business Plus among its supported editions, plus Enterprise, Education, Essentials and Nonprofits editions.
Use trust rules on higher editions. Drive trust rules are listed for Frontline Plus, Enterprise Standard and Enterprise Plus, Education Standard and Education Plus, and Enterprise Essentials Plus. Most small companies on Business editions won't have them, and don't need them to get the basics right.
Share only free/busy on calendars. The small business checklist suggests limiting external calendar sharing to free/busy information, under Apps > Google Workspace > Calendar > Sharing settings (calendar sharing options; no edition limit stated).
Gmail protection
Google's small business checklist has three Gmail items. None of the three help pages below lists an edition limit.
Turn on enhanced pre-delivery message scanning. Under Apps > Google Workspace > Gmail > Spam, Phishing and Malware, this setting holds suspicious messages briefly so Gmail can run extra checks before delivery. Google's pre-delivery scanning page is upfront about the cost: delivery of flagged messages is slightly delayed. You need the Gmail Settings administrator privilege.
Turn on advanced phishing and malware protection. Under Apps > Google Workspace > Gmail > Safety, Google's advanced protection settings cover risky attachments, hidden and suspicious links, and spoofing such as look-alike domains and messages pretending to come from your own domain. For each, you choose to keep the message in the inbox with a warning (the default), move it to spam, or quarantine it. Each section also has an option to apply future recommended settings automatically, which saves you checking back.
Set up SPF, DKIM and DMARC. SPF is a TXT record at your domain host, not a setting in the Admin console, and it helps keep your outgoing mail out of recipients' spam folders. Google's SPF page recommends DKIM and DMARC alongside it, and says bulk senders, which it defines as more than 5,000 messages a day, are required to set up all three.
Get alerts by email. The alert center in the Admin console collects notifications about potential problems in your domain, and you can set up email notifications for its alerts with a rule. Google's page ties starting an investigation from an alert to Enterprise editions; viewing alerts and emailing them has no edition limit stated there.
Leavers
Google's page on keeping data secure after an employee leaves lists, in order: wipe their mobile devices, remove their recovery email and phone, change their password, revoke OAuth application tokens, reset sign-in cookies, revoke security keys and app passwords, and finally transfer what you need and delete the account. These pages name no edition limit for suspension, cookie resets or deletion.
Suspension is still billed. Suspended accounts are charged at the same rate as active ones on Annual and Flexible plans. Suspend on the last day, then decide quickly whether to delete or archive.
Resetting sign-in cookies is not a full sign-out. It signs the user out of browsers and mobile devices, but not out of apps such as Gmail and Drive for desktop, per Google's sign-out page. Suspending a user resets their cookies automatically.
Deleted users can be restored for 20 days. That's the window on Google's deletion page. Transfer Drive files and calendars before you delete, not after the window closes.
Google is not the whole job. None of these steps removes the person from Slack, GitHub or your CRM, and a tool where they set a password keeps working. Google Workspace offboarding walks through the full Google sequence, and orphaned accounts covers what's left behind elsewhere.
The checklist
| Setting | Where | Edition (per Google's page) |
|---|---|---|
| Enforce 2SV for everyone, admins first | Security > Authentication > 2-step verification | No limit stated |
| Security keys for super admins | 2SV methods; admin best practices | No limit stated |
| Two super admins, separate daily accounts | Directory > Users > user > Admin roles and privileges | No limit stated |
| Recovery details on admin accounts | Directory > Users > user > Security | No limit stated |
| Super admin self-recovery off | Security > Authentication > Account recovery | Default off on Business Plus and some others; on elsewhere |
| Narrow admin roles for everyone else | Directory > Users > user > Admin roles and privileges | No limit stated |
| Multi-party approval for sensitive changes | See Google's multi-party approval page | Enterprise Standard/Plus, Education Standard/Plus, Enterprise Essentials Plus |
| Review accessed third-party apps | Security > Access and data control > API controls | No limit stated |
| Restrict unconfigured apps to sign-in only | API controls > Settings | Not in Education editions |
| Warn on external sharing; private link default | Apps > Drive and Docs > Sharing settings | All editions |
| Calendar external sharing: free/busy only | Apps > Google Workspace > Calendar > Sharing settings | No limit stated |
| Enhanced pre-delivery scanning | Apps > Gmail > Spam, Phishing and Malware | No limit stated |
| Advanced phishing and malware protection | Apps > Gmail > Safety | No limit stated |
| SPF, DKIM, DMARC | Your domain host (DNS) | No limit stated |
| Leaver sequence: wipe, reset, revoke, delete | Directory > Users > user > Security | No limit stated |
Run the whole table once, then check the third-party apps list and the admin list every quarter.
Where SmashSSO fits
Google Workspace security ends at Google's edge. When someone leaves, suspending them in Google stops new Google sign-ins, but their accounts in your other tools stay until somebody removes them. SmashSSO reads your people from Google Workspace with read-only directory access, alerts you when someone is suspended, and shows every tool where they still have an account, matched by email. You remove them from there, through a tool's member API where you have added a token or an agent in your own Chrome otherwise.
It does not change any Google Workspace setting, enforce 2SV or review OAuth apps, and it is not SSO. It costs a flat fee from $199 a month, billed annually (pricing). The quarterly user access review is where both lists, Google's and your tools', get checked together.