Google Workspace for Nonprofits: Hong Kong Setup Guide
How Hong Kong NGOs can apply for free Google Workspace for Nonprofits, set up professional email, and configure SPF, DKIM and DMARC the right way.

Many Hong Kong NGO staff still send and receive institutional email through personal Gmail accounts — not out of neglect, but simply because they don't know their organisation likely qualifies for a free professional Google Workspace plan. Google for Nonprofits is that programme: it's built for eligible nonprofits, but the application process and eligibility requirements do have a few steps that commonly trip people up.
What is Google for Nonprofits, and does your Hong Kong organisation qualify?
Google for Nonprofits is a suite Google offers to registered nonprofit organisations, centred on a nonprofit edition of Google Workspace (institutional email, Drive, Meet, and more), alongside other tools like Google Ad Grants and the YouTube Nonprofit Program.
General eligibility typically covers a few areas (always confirm the latest specifics against Google's own review criteria):
- The organisation is formally registered as a charity or nonprofit, with the relevant registration documents
- The organisation's purpose is nonprofit and doesn't involve discriminatory policy
- Government bodies, schools, and hospitals are not eligible under this programme (these have separate Google offerings)
Hong Kong organisations applying typically need to provide documentation proving their charitable status — for example, a Section 88 tax-exemption certificate from the Inland Revenue Department, or a society/company registration certificate — to establish the organisation's legal nonprofit identity.
What do you need to prepare before applying?
The step where applications most often stall isn't on Google's side — it's the organisation's own paperwork not being in order:
- Formal registration documents — society/company registration certificate, charitable status documentation
- A domain the organisation actually owns — this is a step many organisations underestimate. If the domain sits under a former staff member's personal account, the application will stall (see our related article on domain ownership)
- Contact details for one responsible staff member — ideally a role-based address (e.g. admin@, it@) rather than a personal email
- Basic organisation information — legal name, address, official website, mission summary
Step-by-step application process
- Register — go to the Google for Nonprofits site and begin the application under the organisation's identity
- Submit organisation details — registration documents, charitable status proof, organisation website, etc.
- Eligibility review — Google typically reviews organisation identity through a third-party verification partner; turnaround ranges from days to weeks depending on how complete your documents are
- Domain ownership verification — once approved, you'll verify domain ownership in the Google Admin Console, usually by adding a DNS TXT record proving you control the domain
- Set up accounts and basic security — create staff accounts and configure two-factor authentication (2FA) and password policies. Many organisations skip this step, but it's the first line of defence against account compromise
Domain ownership: the step you must sort out before applying
If you're not confident the organisation's domain is actually owned by the organisation — rather than sitting under an individual's personal account — this needs to be resolved first. It's not just about the Google for Nonprofits application; it affects the long-term stability of your website and email. We recommend doing a domain ownership check before starting the Workspace application. See our related guide, "NGO Domain Ownership: Build a Digital Asset Register."
Setting up SPF / DKIM / DMARC: keeping your email out of spam folders
Once you're on Workspace, there's one more step many organisations don't realise they need: setting up SPF, DKIM, and DMARC — three email authentication records. In plain terms, these tell other mail servers, in a verifiable way: "this message really was sent by our organisation." Without them, your outgoing emails (donation receipts, event notices) are more likely to land in spam or never reach recipients at all. This step is fairly technical — if no one on staff has relevant experience, it's worth bringing in professional help to set up once, properly.
Onboarding and offboarding: get ahead of future problems
Once you've applied for institutional email, set up a clear onboarding/offboarding process: new staff use organisation accounts from day one, never personal Gmail for organisational matters; when someone leaves, revoke their account access immediately and hand off any files, donor records, or client information they had access to. This one habit is what makes institutional email actually worth having.