Most NGOs do not set out to become experts in email infrastructure. A founder registers a domain, someone signs up for a few accounts, volunteers are added in a hurry, and two years later nobody is sure who can see the donor spreadsheet. This Google Workspace setup checklist for NGOs and nonprofits is meant to prevent that drift. It walks through eligibility, domain and email authentication, volunteer accounts, shared drives, offboarding and donor-data access control, in the order you would normally do the work.
Use it as a working document. Tick items off, assign an owner to each one, and keep a copy for your trustees. If you would rather have an experienced team run the migration, our Google Workspace setup service covers the same ground with a planned handover.
Why nonprofits need a different setup from a business
A small company usually has stable staff, a single office and a clear owner for every system. An NGO often has the opposite profile, and the setup should reflect that.
- High turnover: volunteers, interns and short-term project staff come and go, so account creation and removal must be routine, not special.
- Sensitive data: donor records, beneficiary details and sometimes case notes are held in ordinary documents and mailboxes.
- Distributed teams: field workers, board members and partners often use personal devices and unreliable connections.
- Funder scrutiny: grantors and auditors may ask who had access to what, and when.
- Limited technical time: there is rarely a full-time administrator, so the configuration has to be simple enough to maintain.
Step 1: Confirm licensing eligibility before you build anything
Google runs a programme that offers Workspace to eligible nonprofits on special terms, and eligibility rules differ by country. Before you plan anything, find out whether your organisation qualifies, because the licence type affects which features and support you can use.
- Gather your registration documents and the legal name exactly as it appears on them.
- Check the current requirements for your country on Google's nonprofit programme pages, since they change and vary by region.
- Decide who will be the verified contact for the application. Use a role-based address, not one person's private mailbox.
- Confirm which edition you will receive and compare its features with what you need, such as shared drives, retention and security controls.
- Keep a note of renewal or re-verification requirements so the licence does not lapse unnoticed.
If your organisation is not eligible, you will use a standard paid plan instead. In that case, ask for an itemised quote so trustees can see exactly what each user and feature costs.
Step 2: Secure the domain and set up email authentication
Donor appeals and receipts only work if they reach inboxes. Email authentication is also what stops someone impersonating your charity to send fake payment requests. This is the most technical part of the checklist, so it helps to understand what each record does.
Own and protect the domain
Register the domain under an organisational account, not a founder's personal login. Turn on registrar lock, enable two-factor sign-in on the registrar account, and record who holds the credentials. Many NGOs lose control of their domain simply because the person who bought it has left.
MX records
MX records tell the internet where to deliver your mail. During migration, you switch these to Google's mail servers. Plan the cutover for a quiet period, lower the record's time-to-live in advance so the change propagates quickly, and keep the old mailboxes available until you have confirmed that mail flows correctly.
SPF
An SPF record lists the services allowed to send mail on behalf of your domain. Besides Google, you may also send through a donation platform, a newsletter tool or a CRM. Each legitimate sender must be included, and you should publish only one SPF record for the domain.
DKIM
DKIM adds a cryptographic signature to outgoing mail so receivers can confirm that a message was not altered. You generate the key in the admin console, publish it in your DNS and then switch signing on. Do this for any third-party sender that supports it as well.
DMARC
DMARC tells receiving servers what to do when a message fails SPF and DKIM checks, and where to send reports. A sensible approach is to start in monitoring mode, read the reports to find senders you forgot, fix them, and then tighten the policy gradually. Moving straight to a strict policy can block your own legitimate fundraising emails.
Step 3: Design accounts, groups and organisational units
Decide on a structure before you create users. A little planning here saves a great deal of cleaning later.
- Use a consistent naming convention for staff addresses.
- Create role-based groups for shared inboxes such as info, donations, volunteers and press, so messages are not trapped in one person's account.
- Create organisational units that match how people actually work, for example staff, volunteers, board members and partners.
- Apply stricter settings to units that touch sensitive data, and lighter ones to short-term volunteers.
- Restrict who can create new groups and who can share outside the organisation.
Step 4: Volunteer accounts and shared drives
Volunteers need access to the files relevant to their work and nothing more. The simplest way to achieve that is to store files in shared drives, not in individual My Drive folders, and to manage access through groups.
Why shared drives suit NGOs
Files in a shared drive belong to the organisation, not to the person who created them. When a volunteer leaves, their work stays where the team can still reach it. That alone removes one of the commonest causes of lost project documents.
A practical structure
- One shared drive per programme or department, not one giant drive for everything.
- A separate, tightly restricted drive for finance and donor records.
- A general drive for public templates and policies that everyone can read.
- Access granted to groups, never to named individuals, so changing a role means changing group membership only.
- Clear role levels: most volunteers as contributors or commenters, a few leads as managers.
Volunteer account basics
Give volunteers organisation accounts rather than asking them to use personal email for charity work. Set an expiry or review date when you create the account, put them in a dedicated organisational unit, and limit external sharing from that unit. Require two-step verification for everyone, volunteers included. Our Google Workspace setup for nonprofits engagements usually begin by agreeing this structure with you before a single account is created.
Step 5: Donor-data access control
Donor and beneficiary information is the most valuable and most sensitive thing your organisation holds. Treat it accordingly, and remember that data protection law in your country may impose specific duties. Take legal advice for those obligations; the points below are about configuration.
- Keep donor lists in one restricted shared drive, not scattered across personal drives and email attachments.
- Limit membership of that drive to the smallest group that needs it and review the list regularly.
- Disable or restrict downloading, printing and copying for the most sensitive files where your edition allows it.
- Block sharing with anyone outside the organisation for that drive, or require an explicit approval step.
- Use data loss prevention rules, if your edition offers them, to flag documents that contain payment or identity details.
- Turn on audit logs so you can later see who opened or shared a file.
- Require stronger sign-in checks for administrators and for anyone with access to donor data.
Step 6: Offboarding, done the same way every time
Offboarding is where most NGOs leak access. A repeatable process matters more than a perfect one.
- Suspend the account on the last day instead of deleting it immediately, so nothing is lost.
- Reset the password and sign the user out of all sessions and devices.
- Remove them from groups, which automatically removes shared drive access.
- Transfer ownership of any files in their personal drive to a named colleague.
- Forward or delegate their mailbox to a manager for a defined period.
- Revoke app passwords, third-party integrations and calendar delegations.
- Remove their access from other systems, such as the donation platform and the CRM.
- Delete the account only after the agreed retention period and with sign-off from the owner.
The complete setup checklist at a glance
The table below turns the steps above into a single page you can hand to your administrator or board. Add a name and a due date against each row.
| Area | What to do | Who should own it | Done when |
|---|---|---|---|
| Licensing | Check nonprofit eligibility, apply, choose the edition | Operations lead | Licence confirmed and renewal date recorded |
| Domain | Register under an organisational account, enable lock and two-factor sign-in | Administrator | Credentials held by two named people |
| MX records | Point mail delivery to Google, lower the time-to-live beforehand | Administrator or provider | Test mail arrives in the new mailboxes |
| SPF | Publish one record covering every legitimate sender | Administrator | Donation and newsletter platforms pass checks |
| DKIM | Generate keys, publish in DNS, switch on signing | Administrator | Signatures show as valid on test messages |
| DMARC | Start in monitoring mode, review reports, then tighten | Administrator | Reports are clean and the policy is enforced |
| Groups and units | Create role-based groups and organisational units | Administrator | Structure agreed before users are added |
| Shared drives | One per programme, plus a restricted finance and donor drive | Programme leads | Access managed only through groups |
| Volunteer accounts | Dedicated unit, review date, limited external sharing | Volunteer coordinator | Every volunteer has an owner and an end date |
| Donor data | Restrict membership, sharing and downloads, enable audit logs | Data protection lead | Access list reviewed and signed off |
| Security | Two-step verification for all users, stricter checks for admins | Administrator | No account without a second factor |
| Offboarding | Suspend, reset, remove from groups, transfer files, delete later | Line manager and administrator | Written process in use for every departure |
What a managed setup costs and how to compare quotes
We do not publish prices in articles because they depend on the size of your team and the amount of mail and data you carry across. These are the factors that move the price of a professional setup.
- The number of mailboxes and shared inboxes to migrate, and how much historic mail must come across.
- Whether you are moving from another provider or starting fresh.
- The number of third-party senders that need to be added to your email authentication records.
- How many shared drives and groups need to be designed and populated.
- Support after launch, including who handles requests when something breaks.
Ask every provider for an itemised quote, so you can see which items are one-off work and which are recurring. Our Google Workspace migration and setup page explains how we scope these projects.
Why Companies Choose CloudHouse for Google Workspace Setup
Organisations come to CloudHouse because we plan delivery in clear stages, stay available for support after launch and give transparent, itemised quotes so you know what each part costs. We aim to leave your team with a setup they can understand and maintain, including written notes on the choices we made.
Conclusion
A well-run Google Workspace gives an NGO reliable email, clear file ownership and a defensible record of who can see donor data. Work through the checklist in order: confirm eligibility, secure the domain, authenticate your email, design groups and shared drives, lock down donor information and make offboarding routine. If you would like help, visit our Google Workspace setup service page and request an itemised quote for your organisation.


