Sectors
Google Workspace for charities and nonprofits
Charities eligible for Google Workspace for Nonprofits receive discounted or no-cost licensing, but the discount is the easy part. The work that matters is volunteer account lifecycle — 30 to 50 per cent of seats in the charity tenants we run — plus donor data access control and a sharing policy that survives high turnover.
| Eligibility | Validated through Google for Nonprofits registration |
|---|---|
| Volunteer accounts | Expiry date set at creation, reviewed monthly |
| Donor data | Restricted org unit, no external sharing permitted |
| Safeguarding | Separate drive, named access list, audited quarterly |
| Common waste | Dormant volunteer accounts consuming seats |
| Our setup engagement | £1,200 / $1,550 fixed for tenants under 100 seats |
Volunteer accounts need an expiry from day one
Staff offboarding has a trigger: someone resigns and HR tells IT. Volunteer offboarding usually has no trigger at all. Someone stops coming, and nothing in any system notices. The only reliable answer is to set an expected end date at account creation and review the list monthly against it.
A monthly fifteen-minute review is unglamorous and completely effective. Accounts past their end date are suspended, and reactivation is trivial if the volunteer returns. The alternative is an annual clear-out that nobody has time for, which is why the accounts are still there three years later.
- Expected end date recorded on every volunteer account at creation
- Monthly review, suspend past the date, reactivate on request
- Volunteers on frontline or restricted licences, not full seats
- No volunteer access to donor or beneficiary data by default
- Group-based access so removal is one action, not five
Donor and beneficiary data
Two data sets carry the real risk. Donor records, because they carry financial and contact information and because a breach damages the fundraising relationship permanently. Beneficiary records, because they frequently contain information about vulnerable people and, in some organisations, safeguarding material.
Both belong in a restricted org unit with external sharing disabled, group-based access, and a quarterly access review with a named owner. Not because a policy document says so, but because the configuration is what actually prevents a well-meaning volunteer from sharing a spreadsheet with an external partner.
Getting eligibility and licensing right
Google for Nonprofits validation is a paperwork exercise that trips organisations up mostly on entity naming and registration numbers not matching. It is worth doing carefully once, because reapplying after a rejection is slower than getting it right initially.
Once validated, the temptation is to give everyone the highest available edition because it costs nothing. That is usually fine for staff and usually wrong for volunteers, because storage and admin surface grow with account count regardless of price, and a tenant with four hundred nominal accounts is harder to secure than one with eighty.
Training the people who will run it
Charity IT is often one person doing it alongside another job, sometimes a trustee, occasionally a volunteer. Any configuration that depends on continuous expert attention will degrade. What works is a short list of routine tasks, written for a non-specialist, with clear escalation for anything outside it.
We write that runbook as part of a setup engagement and record a training session that new administrators can watch when the current one moves on, which in this sector they reliably do.
What we see that others don't say
Volunteer turnover, not staff turnover, is what breaks charity tenants: accounts issued for a six-week campaign are almost never reclaimed, and a tenant three years into that pattern typically holds more dormant volunteer accounts than active staff ones.
What this doesn't cover
- We do not handle your Google for Nonprofits eligibility application on your behalf, though we will tell you exactly what documentation it needs.
- We do not advise on charity law, safeguarding policy or data protection obligations. We implement the controls your policy specifies.
- Donation platforms, CRM systems and fundraising tools sit outside Workspace and outside this scope beyond their OAuth grants.
- Discounted licensing does not extend to every Google product; some services remain chargeable regardless of nonprofit status.
Questions we get asked
- Is Google Workspace free for charities?
- Eligible organisations receive discounted or no-cost licensing through Google for Nonprofits after validation. Eligibility criteria vary by country, and not every Google product is included in the discount.
- How should charities handle volunteer accounts?
- Record an expected end date at account creation and review monthly, suspending accounts past their date. Volunteers should hold restricted licences and have no default access to donor or beneficiary data.
- Where should donor data live in Workspace?
- In a restricted org unit with external sharing disabled and group-based access, reviewed quarterly by a named owner. Configuration prevents accidental sharing in a way that a policy document cannot.
- Who should administer a small charity's Workspace tenant?
- Ideally two people, so absence and turnover do not leave the tenant unmanaged, working from a written runbook aimed at non-specialists with a clear escalation path for anything unusual.
How this page is verified
Reviewed by Deepak Shukla, Founder, Pearl Lemon Cloud. Last checked .
- Google for Nonprofits eligibility and licensing behaviour reflect Google's nonprofit programme documentation as of 2026-08-06.
- Dormant-account observations are Pearl Lemon Cloud audit findings across nonprofit tenants to 2026-08-06.
- Setup pricing is the Pearl Lemon Cloud rate card as of 2026-08-06.
Sources you can check
Related pages
Set up a charity tenant properly
Fixed-fee setup for tenants under a hundred seats, including volunteer lifecycle, donor data controls and a runbook written for non-specialists.