Google Workspace for Nonprofits: The Admin Guide Nobody Gave You

Google for Nonprofits gives eligible organizations free access to Google Workspace — up to 2,000 user accounts and 100TB of shared storage. The signup process through TechSoup is well-documented. Google's own getting-started wizard walks you through domain verification, MX records, and creating your first few accounts.

What happens after that? Not much guidance at all.

This guide covers the admin tasks that the setup wizard doesn't mention — the ones that cause real problems six months or two years down the road, when accounts have piled up, nobody remembers who has admin access, and a departing board member takes institutional knowledge with them.

You're the Admin Now

In most nonprofits, there is no IT department. The person who set up the Google Workspace account is the IT department. Usually the founder, a board member, or whichever staff member was tech-savvy enough to figure out domain verification and DNS records.

If that's you, this guide is for you.

You're not failing at this. Google Workspace is enterprise software designed for organizations with dedicated IT teams. The Admin Console assumes someone is looking at it regularly, reviewing alerts, managing user lifecycles. That's a reasonable assumption for a company with 500 employees and a sysadmin. It's not reasonable for a nonprofit where the executive director is also handling grant applications, donor relations, and event planning.

The good news: most of the critical admin work doesn't require deep technical knowledge. It requires awareness of what to do, and a reminder to actually do it.

The First Things to Get Right

These are the tasks that matter most and cost you nothing. Do them this week.

Assign a Second Super Admin

This is the single most important thing on this list. If your organization has one Super Admin account and that person leaves the organization, loses access to their email, or simply forgets the password — you are locked out of your own domain. Google's account recovery process for nonprofits is slow, painful, and not guaranteed to work.

The scenario shows up constantly in admin forums: a founder leaves the board, their personal email was the Super Admin, nobody else has access, and now the organization can't add new staff accounts or reset passwords.

Fix it now:

Log in to the Admin Console at admin.google.com
Go to Account > Admin roles
Assign Super Admin to at least one other trusted person
Make sure both Super Admins use accounts on your organization's domain, not personal Gmail addresses

Use an Organizational Admin Account

Your Super Admin account should be on your org's domain (e.g., admin@yournonprofit.org), not someone's personal Google account. If the person who set things up used their personal Gmail as the primary admin, create a proper admin account on the domain and transfer Super Admin privileges to it.

Enforce Two-Factor Authentication

Go to Security > Authentication > 2-step verification and enforce it for all admin accounts at minimum. Ideally, enforce it org-wide. This is the highest-impact security measure you can take, and it's free.

Document Who Has Admin Access

Write down — in a shared document or internal wiki — who has admin access, what level they have, and why. This sounds obvious, but most organizations cannot answer this question without logging into the Admin Console and clicking through individual user accounts.

For a deeper walkthrough on auditing admin roles, see our guide: Who Has Admin Access? How to Audit Google Workspace Roles.

User Management Without an IT Team

Google Workspace user management is straightforward when you have five accounts. It gets confusing at twenty, and it's a mess at fifty — especially without someone dedicated to maintaining it.

Creating and Removing Accounts

When new staff or long-term volunteers join, creating their account is the easy part. The hard part is everything that happens when they leave: transferring email, removing them from groups, reassigning document ownership, and deciding whether to suspend or delete the account.

Suspend vs. delete: When someone departs, always suspend first. A suspended account preserves all data — email, Drive files, Chat history — but prevents the person from signing in. Deletion is permanent and removes data that may be subject to retention requirements. Suspend the account, handle data transfers, and only delete after you've confirmed nothing is needed.

Finding Inactive Accounts

Google Workspace charges per user on paid plans, but even on the free nonprofit tier, unused accounts create clutter and security risk. The problem is that the Admin Console makes it genuinely difficult to find inactive users. You can't sort by last login date. You can't filter by activity level. The default user list gives you names, emails, and status — and that's about it.

Many admins resort to exporting the user list to a spreadsheet, manually checking login dates, and trying to figure out who's still active. If that sounds familiar, you're not alone — and there are better approaches. See: Stop Exporting to Google Sheets to Manage Workspace Users.

Volunteer Turnover: The Nonprofit-Specific Problem

Every organization deals with employee departures. Nonprofits deal with something harder: constant volunteer turnover.

Volunteers join for a semester, a project, or a season. They get a Google Workspace account so they can access shared drives and receive group emails. Then they leave — sometimes with a clear end date, sometimes by simply going quiet.

Each departure needs, at minimum:

Email forwarding set up so messages to their address reach someone active
Group removal from every Google Group they belonged to
Document ownership transfer for any files they created
Account suspension once the above is handled

Most nonprofits skip some or all of these steps. The result: accounts pile up, groups contain more former volunteers than current ones, and shared drives have orphaned files that nobody can edit.

If you're dealing with a backlog, start with the volunteer offboarding checklist — it's adapted from the general offboarding checklist specifically for the nonprofit reality of less notice, higher volume, and no HR department triggering the process.

Google Groups: Your Silent Mess

Nonprofits rely on Google Groups more heavily than most organizations. Board communications, committee threads, donor contact lists, volunteer coordination, event planning — Groups handles all of it.

The problem is that Groups accumulate departed members faster than any other part of your Workspace. A board committee group that was created three years ago might have three current members and twelve people who rotated off the board in 2024. A volunteer coordination group might include staff who left eighteen months ago.

This isn't just clutter. A group with outdated members is a data exposure risk. Every email sent to that group reaches people who should no longer have access to your internal communications.

Google Groups cleanup is tedious in the Admin Console because there's no bulk editing and no way to cross-reference group membership against active users. For a practical approach to fixing this, see: Your Google Groups Are a Mess. Here's How to Fix Them.

Licenses: You're Probably Fine, But Check

The free Google Workspace for Nonprofits plan covers what most small-to-midsize nonprofits need: Gmail, Drive, Calendar, Meet, Chat, and basic admin controls. You don't need to upgrade unless you have specific requirements.

When upgrading makes sense:

Google Vault — if you need eDiscovery, legal holds, or compliance-grade data retention (common for organizations handling government grants or operating in regulated sectors)
Advanced endpoint management — if staff use organization-owned devices that need remote wipe capability
App-level security policies — DLP rules, advanced phishing protection beyond the free tier

When upgrading does not make sense:

Don't upgrade the entire organization just because one person needs Vault. Google allows per-user license assignments. Upgrade the specific accounts that need advanced features, and keep everyone else on the free plan.

For more on managing license costs intelligently, see: How to Reduce Google Workspace License Costs Without Losing Features.

The Board Transition Problem

Board members rotate every one to three years. This is normal governance. It becomes an IT problem when a board member was the person who originally set up the Google Workspace account, configured the domain's DNS, or holds Super Admin access.

When that board member's term ends, their departure is not just a governance event — it's a critical IT event.

Create a digital succession document that includes:

Who set up the domain and where it's registered
Who holds DNS access (registrar login credentials)
Who the current Super Admin accounts are (and their recovery emails)
Where the organization's password manager or credential vault lives
Who to contact at Google for Nonprofits if account recovery is needed

This document should live with the organization — in a shared drive accessible to leadership, in a physical binder at the office, or in a password manager's secure notes. It should not live exclusively in one person's memory or personal account.

Update it every time the board changes or admin access is reassigned. If you're already in the situation where nobody has Super Admin access, the lost super admin recovery guide walks through every path to get it back.

You Don't Need an IT Department for This

Most of what's in this guide boils down to: check a few things regularly, have a process for departures, and don't let one person hold all the keys.

If your organization has outgrown the "one person managing everything in the Admin Console" phase but hasn't reached the "hire a sysadmin" phase, that gap is where most nonprofit IT disasters happen. MonitorWorkspace was built for exactly that gap — user activity, group health, offboarding, admin role visibility, all in one dashboard. The free tier covers up to 10 users. For most small nonprofits, that's the whole team.