Google Workspace Security Setup: Enforce 2-Step Verification, Passkeys, Password Rules and Recovery
A stolen password is still the most common way a small business loses its Google Workspace account, and everything behind it. The fix is a short list of Admin console settings that take minutes each. Here they are in the right order, starting with enforcing 2-Step Verification without locking anyone out.
Before you start
Sign in at admin.google.com as a super admin; enforcing 2-Step Verification (2SV) and changing account-recovery settings are super-admin-only tasks (see our Admin console beginner’s guide).
- Do the steps in order. Recovery details and backup codes come before enforcement, so you can’t lock yourself out.
- Warn your users first. Google’s rollout advice starts with telling people what 2SV is, the deadline and the recommended method.
- Check your plan. Everything here is in every Business plan, including Business Starter at $8.28 per user/month, except session-length control and Google Vault (Business Plus, $25.83) and the Enterprise-only security center and Context-Aware Access. See current pricing.
The 10-point Google Workspace security checklist
Our order for every new business or family domain. It covers Google’s security checklist for small businesses (1–100 users) plus the admin-account safeguards Google recommends separately.
| # | Setting | Where in the Admin console | Time |
|---|---|---|---|
| 1 | Second super admin | Directory → Users → user → Admin roles and privileges | 5 min |
| 2 | Recovery phone and email for admins | Directory → Users → user → Security → Recovery information | 5 min |
| 3 | Backup codes for admins | Directory → Users → user → Security → 2-step verification | 5 min |
| 4 | Allow, then enforce 2SV (no SMS) | Security → Authentication → 2-step verification | 15 min + enrollment window |
| 5 | Allow passkeys | Security → Authentication → Passwordless | 2 min |
| 6 | Password rules: strong, 12+ characters, no reuse, no expiry | Security → Authentication → Password management | 3 min |
| 7 | User account recovery; super admin recovery decision | Security → Authentication → Account recovery | 3 min |
| 8 | Drive external-sharing warning, highlight external files | Apps → Google Workspace → Drive and Docs → Sharing settings | 5 min |
| 9 | Calendar: free/busy only for outsiders | Apps → Google Workspace → Calendar → Sharing settings | 3 min |
| 10 | Gmail safety settings; Alert Center notifications | Apps → Google Workspace → Gmail → Safety; Security → Alert center | 10 min |
14-day free trial · 10% off your first year with our referral link
Step 1: Enforce 2-Step Verification (without locking anyone out)
2-Step Verification (2SV, often called 2FA) means a password alone no longer opens an account. Users can turn it on themselves; a business should enforce it, following the allow-then-enforce sequence on Google’s Deploy 2-Step Verification page.
1. Protect your admin account first
Enforcement applies to admins too, so build the safety net first:
- Add a second super admin:
Directory → Users, open the person,Admin roles and privileges, switchSuper AdmintoAssigned, save. Google’s admin best practices call for more than one super admin, each a different person; our admin roles guide covers the other roles. - Add recovery details to both admin accounts:
Directory → Users → (user) → Security → Recovery information. - Print backup codes: on the same Security page, under
2-Step Verification, clickGet backup verification codes. Each set holds 10 single-use codes; a new set invalidates the old one. Store them away from the admin’s phone.
2. Allow 2-Step Verification and tell your users
Go to Security → Authentication → 2-step verification, select your top-level organization, check Allow users to turn on 2-Step Verification, leave Enforcement at Off and save.
Then email everyone the deadline and one instruction: open your Google Account → Security → 2-Step Verification. Google ranks security keys as the strongest method because they stop phishing outright; a passkey on a phone or laptop comes close; Google prompt and authenticator apps are good everyday options; text and voice codes are weakest because they can be intercepted. Our suggestion: Google prompt or a passkey for everyone, a security key for each admin.
3. Choose the allowed methods
Any: includes SMS and voice codes. Fine for a family domain where a grandparent signs in from a tablet.Any except verification codes via text, phone call: our pick for businesses. Prompts, authenticator apps, passkeys and keys keep working; nobody falls back to SMS.Only security key: the gold standard once every person owns two keys. Admins generate backup codes in this mode.
Leave Allow user to trust the device checked unless staff share computers.
Heads-up: Google warns that anyone enrolled with SMS only is locked out at enforcement if you choose “Any except…”. Have them add Google prompt first.
4. Set the enrollment period and the enforcement date
New user enrollment period: how long a newly added user can sign in with only a password, from 1 day to 6 months. One week suits a new hire.Enforcement:Onstarts now;Turn on enforcement from datelets you pick a date, which Google says can take effect 24–48 hours later. Pick one to two weeks out and save.
That window is for enrollment; check the report in step 6 twice and nudge stragglers.
5. Exempt shared and kiosk accounts with an organizational unit
A front-desk Chromebook, a shared info@ mailbox or a scanner that sends email can’t tap a phone prompt. Google has no exempt-this-user switch; the supported workaround is an organizational unit (OU) where enforcement stays off:
Directory → Organizational units: create a child OU calledShared accounts.- Move those accounts into it (tick the user in
Directory → Users,Change organizational unit). - On the 2-step verification page select
Shared accounts, setEnforcementtoOff, save.
Keep it tiny. Shared mailboxes are better as a Google Group or Gmail delegation, which need no shared password, and a kiosk account can still enroll a security key kept at the desk.
6. Check that it worked
Reporting → User reports → Security shows 2SV enrollment and enforcement per user, up to 48 hours behind; a user’s Security page in the Admin console is live. After the date, anyone who never enrolled is blocked at sign-in and needs a backup code from you (see troubleshooting).
Heads-up: Google is phasing in mandatory 2SV for admin accounts regardless of your settings. As of October 2026 it covers Education, Nonprofits, Cloud Identity, Android Enterprise and Enterprise customers on third-party SSO, with more to follow; affected admins get notice, then lose mobile access after 15 days and web access after 30.
Step 2: Allow passkeys and set password rules
Turn on passkeys (passwordless sign-in)
A passkey signs someone in with a fingerprint, face, screen-lock PIN or security key: no password typed, nothing to phish. Users can already add a passkey as a 2SV method; the admin setting controls whether they may skip the password entirely, and it is off until you turn it on.
Security → Authentication → Passwordless.- Check
Allow users to skip their password and authenticate with a passkey, save. - Each user creates a passkey from the Security page of their Google Account and turns on skip password.
Passwords stay as a fallback, and users don’t need 2SV enrolled for this. Leave the Passkeys restriction option alone unless everyone owns a hardware key; it disables phone and laptop passkeys. Check: sign out and back in, and you’re asked for your passkey instead of a password.
Set a sensible password policy
With 2SV enforced, passwords matter less, but still matter. At Security → Authentication → Password management:
Enforce strong password: check.Length: minimum 8–100 characters; set12.Enforce password policy at next sign-in: check, or weak passwords linger.Allow password reuse: uncheck.Expiration: leave off, the default. Forced rotation breedsSummer2026!-style passwords and NIST guidance advises against it; change passwords when there’s a reason, such as a departure or suspected breach.
Add a password manager (Chrome’s built-in one is fine) so long, unique passwords are realistic.
Step 3: Account recovery for users and super admins
Google Workspace account recovery differs from personal Gmail: by default a user who forgets a password asks an admin. Two settings change that.
Let users recover their own accounts
Security → Authentication → Account recovery → User account recovery: check Allow users and non-super admins to recover their account, save. Users need a recovery phone or email; Google notes that users with 2SV can only recover through the recovery email, so ask everyone to add one, or enter it for them under Security → Recovery information when you add new users. Two caveats from the same page: it has no effect with third-party SSO or Password Sync, and when someone leaves, deleting their recovery details isn’t enough because the old details keep working for a while. Reset the password and suspend the account (our offboarding guide has the sequence).
Decide how super admins get back in
Just below, Super admin account recovery has one checkbox: Allow super admins to recover their account. It is on by default for Business Starter and Standard and off for Business Plus. Google recommends turning it off once two super admins can reset each other, because a self-service recovery flow on your most powerful account is exactly what an attacker wants. A solo founder with no second admin should leave it on and keep recovery details current.
If a super admin is locked out, the other super admin resets the password or generates backup codes from the user’s Security page. With no second admin, click Need help? on the admin sign-in page; Google’s recovery wizard can ask you to prove you control the domain, so keep your registrar login findable.
Step 4: Login challenges, session length and app passwords
Login challenges
Separately from 2SV, Google challenges sign-ins that look unusual (new country, odd hour, unfamiliar device) with a phone confirmation, a code to the recovery phone, the recovery email or, if enabled, an employee ID. Nothing to configure, and one more reason every account needs recovery details. The employee-ID option at Security → Authentication → Login challenges isn’t shown to users with 2SV or SSO, so skip it. What you will use: when a legitimate user is stuck, open Directory → Users → (user) → Security → Login challenge and click Turn Off For 10 Minutes.
Session length
A Google web session lasts 14 days by default. Business Plus and Enterprise can change that at Security → Access and data control → Google Session control (shorter for staff handling money or client data, never expire for a kiosk OU); Business Starter and Standard can’t. Every edition can force one person out everywhere: on their Security page click Sign-in cookies → Reset, the first move when a laptop goes missing.
App passwords and the end of “less secure apps”
The old Less secure apps switch is gone from the Admin console, and since May 1, 2025 Workspace accounts no longer accept sign-ins from apps or devices that use only a username and password. Modern clients (new Outlook, Apple Mail, Thunderbird, iOS Mail) use OAuth, which works with 2SV and passkeys; classic Outlook needs GWSMO. The exception is an app password: a 16-digit code a user generates at myaccount.google.com/apppasswords for a device that can’t do OAuth, typically an office scanner. They exist only when 2SV is on for that user, are hidden for security-key-only accounts, and can be revoked from the user’s Security page under Application-specific password. One per device, revoked when it’s retired.
14-day free trial · 10% off your first year with our referral link
Step 5: Sharing defaults, Gmail safety and the Alert Center
Drive
Apps → Google Workspace → Drive and Docs → Sharing settings. Under Sharing options, sharing outside your organization is On, Off or limited to Allowlisted Domains (your accountant, your agency). Most small businesses need it on; if so, enable the warning users see before sharing externally and check Highlight external files. Under General access default, leave new files Restricted (private to the owner), the default. Team files belong in shared drives, where membership is explicit.
Calendar
Apps → Google Workspace → Calendar → Sharing settings. For external sharing of primary calendars choose Only free/busy information (hide event details): outsiders see when you’re busy, not who you’re meeting. Internally, Share all information suits a small team.
Gmail
Two pages. Apps → Google Workspace → Gmail → Spam, Phishing and Malware: check Enhanced pre-delivery message scanning. Then Gmail → Safety:
- Attachments: encrypted attachments, attachments with scripts and anomalous attachment types from untrusted senders. The default is
Keep email in inbox and show warning; we set the first two toMove email to spam. - Links and external images:
Identify links behind shortened URLs,Scan linked images,Show warning prompt for any click on links to untrusted domains. Check all three. - Spoofing and authentication: look-alike domains, spoofed employee names, mail spoofing your domain, unauthenticated mail, spoofed Groups. Check all, plus
Apply future recommended settings automatically.
These work best when your own mail is authenticated, so set up SPF, DKIM and DMARC.
Alert Center
Security → Alert center reports leaked passwords, suspicious logins Google blocked, employee-name spoofing, malware found after delivery and compromised devices. It’s in every Business edition and almost nobody opens it, so turn on email notifications to an address you read.
SSO, Business Plus and Enterprise: when to go further
When SSO with Okta or Microsoft Entra makes sense
“Google Workspace SSO” means two things. If your people live in Google, Google is your identity provider: Workspace signs users into Slack, Zoom, Salesforce and hundreds of other SAML apps, and your 2SV policy covers them all. Third-party SSO is the reverse: staff sign in through Okta or Microsoft Entra ID and Google trusts it. It is set up at Security → Authentication → SSO with third party IdP with a SAML or OIDC profile (a preconfigured Microsoft Entra OIDC profile exists), assigned to OUs or groups so you can pilot it with one team, and it makes sense once you already run an identity provider for a Microsoft estate or dozens of SaaS apps. Two caveats: super admins sign in directly with Google, not through the newer SSO profiles, so keep 2SV on them at both ends; and the user account-recovery setting doesn’t apply to SSO users. A 5–50 person company with no identity provider gets most of the benefit from enforced 2SV plus passkeys, for free.
What Business Plus and Enterprise add
Everything above works on Business Starter ($8.28) and Business Standard ($16.56). Business Plus ($25.83 per user/month) adds Google Vault for retention and eDiscovery, advanced endpoint management and the session control from step 4. The security center (dashboard, investigation tool, security health page), Context-Aware Access (rules like “Drive only from managed devices”) and data loss prevention rules are Enterprise Standard and Plus features as of October 2026, not Business Plus; check Google’s edition list before upgrading for them. Our plan comparison has the full table.
Security also stops at the keyboard: a security key doesn’t help on a laptop full of malware. Chromebooks boot verified, update themselves, sandbox every tab and can be centrally managed, which is why they pair well with a locked-down domain; see our Chromebook guide for small businesses.
Troubleshooting: lockouts, lost phones and codes that never arrive
- A user missed the enforcement date.
Directory → Users → (user) → Security → 2-step verification → Get backup verification codes; send one code and they can sign in and enroll. Google advises against turning 2SV off for the user, and the button is unavailable while enforcement is on anyway. - Lost or replaced phone. Same fix; then they remove the old phone from their 2SV settings and add the new one. A lost security key is removed under
Passkeys & security keyson the user’s page. - Codes aren’t arriving by text. Poor signal or carrier delay: give a backup code now and move them to Google prompt or an authenticator app. With “Any except verification codes via text, phone call”, SMS doesn’t work by design.
- Stuck on a login challenge (new phone, abroad). Security page →
Login challenge → Turn Off For 10 Minutes, then sign in right away. - The scanner or an old app stopped sending email. That is the less-secure-apps shutdown: create an app password (2SV must be on for that account) or switch the device to OAuth.
- Only super admin, locked out, no codes.
Need help?on the admin sign-in page, prove domain ownership through DNS, then add the second super admin you skipped.
14-day free trial · 10% off your first year with our referral link
Related setup guides
- All Google Workspace setup guides
- Google Workspace Admin Roles & Super Admin
- Google Workspace Admin Console: Beginner’s Guide
- How to Add Users to Google Workspace
- Google Workspace Shared Drives: Setup Guide
- Google Workspace Backup & Data Export
- Google Workspace Employee Offboarding Checklist
Frequently asked questions
Is 2-Step Verification free in Google Workspace?
Yes. 2-Step Verification, passkeys, password rules, account recovery and the Gmail safety settings are included in every Google Workspace edition, including Business Starter. You only pay extra for optional hardware security keys or for Enterprise-only tools such as the security center and Context-Aware Access.
How do I enforce 2-Step Verification in Google Workspace?
Go to Security → Authentication → 2-step verification, check Allow users to turn on 2-Step Verification, give people one to two weeks to enroll, then set Enforcement to On or pick a start date. Choose Any except verification codes via text, phone call to block SMS, and exempt shared accounts through an organizational unit where enforcement stays off.
What happens to users who haven’t enrolled when enforcement starts?
They can’t sign in until an admin helps. Generate backup verification codes from the user’s Security page in the Admin console and send one; they sign in with their password and the code, then finish enrolling. Google advises against turning 2SV off for the user, and that option is unavailable while enforcement is on.
What is the difference between 2-Step Verification and passkeys?
2-Step Verification adds a second step after the password, such as a phone prompt, an authenticator code or a security key. A passkey replaces the password: the user unlocks a device with a fingerprint, face or PIN and the device proves who they are, so there is nothing to phish. An admin must allow passkeys before users can skip the password.
Should I make Google Workspace passwords expire?
No. Expiration is off by default in Google Workspace, and current NIST guidance advises against routine rotation because it leads to predictable patterns. Enforce strong passwords with a 12-character minimum, block reuse, enforce 2-Step Verification, and reset passwords only when there is a reason, such as a departure or a suspected compromise.
Can I still use app passwords with Google Workspace?
Yes, but only on accounts with 2-Step Verification turned on, and only for apps or devices that cannot use OAuth, such as an office scanner. The less secure apps setting was removed, and since May 1, 2025 Workspace no longer accepts plain username-and-password sign-ins from third-party apps. Admins can revoke app passwords from the user’s Security page.
Does Google Workspace support SSO with Okta or Microsoft Entra ID?
Yes. Google Workspace supports SAML and OIDC single sign-on with third-party identity providers, including a preconfigured Microsoft Entra profile, configured under Security → Authentication → SSO with third party IdP and assigned per organizational unit or group. It suits companies that already run an identity provider; a small team without one gets most of the benefit from enforced 2-Step Verification and passkeys.
MyOwnGoogle is reader-supported. If you start a Google Workspace trial through our links we may earn a commission, at no extra cost to you. This never affects what we recommend.