Google Workspace for Churches — A Complete Setup Guide

Managing a parish or church with a tangle of personal Gmail accounts, shared passwords, and documents scattered across USB sticks is more common than it should be. Google Workspace gives your church a professional, secure, and collaborative home for email, documents, calendars, and video calls — all under your own domain name. This guide covers everything from applying for the free nonprofit tier to configuring accounts for your team.

Google for Nonprofits: free Workspace for registered charities

The single most important thing to know before you spend anything: if your church is a registered charity in the UK, Google Workspace is free through the Google for Nonprofits programme. This gives you Workspace Business Starter — normally £5.20 per user per month — at no cost.

What you need to qualify

A registered charity number from the Charity Commission for England and Wales, the Scottish Charity Regulator (OSCR), or the Charity Commission for Northern Ireland
A verified domain name (e.g. stmarksparish.org.uk)
TechSoup UK validation — Google uses TechSoup to verify nonprofit status

Catholic parishes in England and Wales are often registered as individual charities, or may fall under a diocesan umbrella charity. Check with your Diocese if you’re unsure of your registration status — many parishes qualify but haven’t applied.

How to apply

Go to google.com/nonprofits and click Get started
Verify your organisation through TechSoup UK (techsoup.org.uk) — you’ll need your charity number and some basic organisational details
Once TechSoup approves you (typically 2–5 working days), return to Google for Nonprofits and activate Workspace
Set up your Workspace account using your church domain

The free tier covers up to 30GB of storage per user and includes Gmail, Drive, Docs, Sheets, Slides, Meet, Calendar, and the Admin console. For most parishes, this is more than enough.

Choosing your domain

Before setting up Workspace you need a domain. If you don’t have one yet:

.org.uk is the most appropriate for a UK parish — costs around £8–12/year
.org is widely recognised and works well internationally — around £10–20/year
.co.uk works but implies a commercial organisation

Your domain name should be stable and permanent. Once parishioners and staff have email addresses at a domain, changing it is painful. Choose something that won’t need updating as clergy or staff change — stmarksparish.org.uk is better than fatherjohnsmith.org.uk.

If you already have a website domain, use that — keep email and web on the same domain for consistency and trust.

Initial Workspace setup

Create your account

Go to workspace.google.com (or through the Google for Nonprofits portal if applying for the free tier). You’ll be asked for:

Your organisation name
The number of users (estimate conservatively — you can add more later)
Your domain name

You’ll create the first admin account during setup. Use a role-based address like [email protected] rather than a personal name — this account is the master key to your Workspace and should outlast any individual.

Verify your domain

Google needs to confirm you own the domain before activating email. You’ll be given a TXT record to add to your DNS settings. If your domain is managed through your hosting provider or a registrar like 123-reg or Namecheap, log in and add the record to your DNS zone. Verification usually completes within a few minutes, occasionally up to 24 hours.

Add MX records

Once your domain is verified, you need to update your MX (Mail Exchange) records to route incoming email through Google. Google provides a standard set of MX records in the Admin console under Domains → Manage domains → Set up Google MX records. Replace any existing MX records at your registrar with Google’s.

This is the step that switches your email over. If you have existing email at the domain, do this during a quiet period and make sure you’ve migrated any important messages first.

Setting up users and accounts

Plan your account structure before creating users

Think about who needs what before you start creating accounts. A typical parish setup might include:

Account	Purpose
`office@`	Main parish contact, seen publicly
`priest@` or `fr.surname@`	Parish priest — personal account
`admin@`	Workspace administration only, not publicised
`safeguarding@`	Dedicated safeguarding contact
`hall@`	Hall bookings enquiries
`newsletter@`	Bulletin and communications
`giving@`	Financial / Gift Aid queries

Avoid creating accounts in the format firstname.surname@ for roles that will turn over — when a volunteer moves on, you’d rather reassign newsletter@ than retire an address that’s been published everywhere.

Creating users

In the Admin console (admin.google.com), go to Directory → Users → Add new user. Fill in the name, email address, and a temporary password. Users will be prompted to change their password on first login.

For role-based accounts shared by multiple people (like office@), consider using Google Groups instead of a user account — see below.

Google Groups as shared inboxes

A Google Group can act as a shared email address without consuming a Workspace licence. Anyone in the group receives emails sent to the group address, and (with the right settings) can reply from that address too.

This is ideal for:

office@ — multiple volunteers monitoring the parish inbox
bookings@ — hall or room booking enquiries
newsletter@ — anyone helping with communications

To set up a group as a shared inbox: Apps → Google Workspace → Groups for Business, then create a group and enable Collaborative Inbox mode.

Gmail configuration

Professional signatures

Every outgoing email from your church is a communication from your organisation. Set up a consistent signature template and share it with all users. A basic parish email signature should include:

Full name and role
Parish name
Website URL
Phone number
Safeguarding notice if appropriate (many dioceses require this)

Workspace admins can push a default signature to all users via Apps → Google Workspace → Gmail → User settings → Signature.

Email routing and aliases

If you’re consolidating multiple old email addresses, set up aliases and routing rules so nothing gets lost. An alias lets one account receive email sent to multiple addresses — useful if you’re retiring an old address but want to catch stragglers.

Admin console → Apps → Google Workspace → Gmail → Default routing lets you redirect mail to the right person or group automatically.

Spam and security settings

Enable these in the Admin console under Apps → Google Workspace → Gmail → Safety:

Enhanced pre-delivery message scanning — catches phishing that bypasses standard filters
Spoofing and authentication protection — prevents spoofed emails impersonating your domain
External recipient warnings — alerts users before they send to addresses outside your organisation

SPF, DKIM, and DMARC

These three DNS records protect your domain from email spoofing and improve deliverability — meaning your emails are less likely to land in recipients’ spam folders.

SPF (Sender Policy Framework) tells receiving mail servers which servers are allowed to send email from your domain. Add Google’s SPF record to your DNS:

v=spf1 include:_spf.google.com ~all

DKIM (DomainKeys Identified Mail) adds a cryptographic signature to outgoing email. Generate your DKIM key in the Admin console under Apps → Google Workspace → Gmail → Authenticate email, then add the provided TXT record to your DNS.

DMARC tells receiving servers what to do with emails that fail SPF or DKIM checks. Start with a monitoring-only policy:

v=DMARC1; p=none; rua=mailto:[email protected]

Once you’re confident your legitimate email is passing authentication, tighten to p=quarantine or p=reject.

Google Drive: document management for your parish

Google Drive replaces the shared folder on someone’s laptop, the emailed attachments, and the USB stick that gets left in the sacristy. Everything lives in the cloud, accessible to everyone who needs it, from any device.

Shared Drives vs My Drive

My Drive belongs to an individual user. If that person leaves, their Drive goes with them — a real problem for organisations that store important documents in personal accounts.

Shared Drives belong to the organisation. Files remain accessible regardless of who created them or whether they’re still a user. For any parish document that needs to outlast a volunteer, use a Shared Drive.

Set up Shared Drives in the Admin console and create a sensible folder structure before people start saving things:

Parish Admin/├── Governance/│   ├── Charity Commission filings│   ├── Meeting minutes│   └── Policies├── Safeguarding/├── Finance/│   ├── Gift Aid│   └── Accounts├── Liturgy/│   ├── Bulletins/│   └── Music/└── Communications/    ├── Newsletter templates    └── Social media

Permissions

Shared Drive access is controlled at the Drive level and the folder level. Keep sensitive folders (Finance, Safeguarding) restricted to named individuals. Give broader read access to general parish resources.

Google Calendar: internal scheduling

Google Calendar sits alongside ChurchSuite rather than replacing it. ChurchSuite owns your public-facing events — the ones that go on your website and that parishioners sign up to. Google Calendar is for your internal team: staff rotas, clergy schedules, meeting bookings, maintenance visits, and so on.

Team calendars

Create shared calendars for different aspects of parish life and share them with the relevant people:

Parish Calendar — all-hands events visible to the full team
Clergy — Fr’s schedule, home visits, hospital visits
Hall Bookings — room usage visible to anyone who manages bookings
Finance — Gift Aid deadlines, accounts submission dates

Calendar sharing settings

Team calendars should be shared within your organisation but not made public — they contain operational detail that doesn’t need to be visible externally. Set sharing to “See all event details” for relevant staff, and “See only free/busy” for the wider organisation.

Embedding a calendar on your website

For a simple internal-use calendar (staff holidays, maintenance schedule) you can embed a Google Calendar on a password-protected page of your website. For your public-facing events calendar, ChurchSuite is the better tool — it handles sign-ups, categories, and featured events in a way Google Calendar doesn’t.

Google Meet: video calls and hybrid worship

Google Meet is included in Workspace and works well for:

Staff and volunteer meetings
Finance committee meetings
Online Alpha or discipleship group sessions
Hybrid arrangements where some attendees join remotely

Meet links are generated directly from Google Calendar events — create a meeting, tick “Add Google Meet video conferencing”, and the link is included in every invitation automatically.

For Sunday Mass or large-scale online worship, YouTube Live (also available through Google for Nonprofits) is more appropriate than Meet — it handles large audiences and allows people to watch without needing a Google account.

Google Forms: simple data collection

Google Forms is useful for low-stakes data collection that doesn’t justify a full ChurchSuite process:

Children’s Liturgy registration (feeding responses into a Google Sheet)
Event interest surveys
Volunteer availability questionnaires
Feedback forms after parish events

Responses feed automatically into Google Sheets, where you can filter, sort, and export them. For anything involving payment, Gift Aid declarations, or formal sign-up management, ChurchSuite is the right tool. Forms is for lightweight, informal collection.

Security: protecting your parish accounts

Two-factor authentication

Enable 2FA for all users. In the Admin console under Security → Authentication → 2-step verification, you can require 2FA organisation-wide. This is the single most effective step you can take against account compromise.

Google Authenticator or a hardware key (YubiKey) is more secure than SMS-based verification. For accounts with access to sensitive data (safeguarding documents, financial records), require a hardware key or authenticator app — not SMS.

Admin account security

Your admin account has access to everything. Protect it accordingly:

Use a strong, unique password stored in a password manager
Require hardware key 2FA
Don’t use the admin account for day-to-day email — create a separate personal account for the administrator
Have a recovery process documented in case the admin leaves unexpectedly

User offboarding

When a volunteer or staff member leaves, act promptly:

Transfer ownership of any Drive files they owned to another user
Set up email forwarding from their account to their replacement
Remove them from all Groups and Shared Drives
Suspend the account (don’t delete immediately — keep it for 30 days in case anything is missed)
After 30 days, delete the account

Document this process so it happens consistently, not just when someone remembers.

GDPR considerations

Google Workspace is GDPR-compliant, and Google acts as a data processor under a Data Processing Agreement that’s built into Workspace terms. However, your church remains the data controller and is responsible for how you use the platform.

Practically, this means:

Don’t store personal data (pastoral notes, medical information, safeguarding records) in personal Drive folders where it could be shared inappropriately
Use Shared Drives with appropriate access restrictions for any sensitive records
Review who has access to what periodically — the Admin console’s reporting tools help with this
Include Google Workspace in your parish’s data audit / Record of Processing Activities if you have one

Migrating from an existing email setup

From personal Gmail accounts

If your parish currently uses personal @gmail.com accounts for church business, migration is straightforward — users simply start using their new Workspace account and archive old correspondence. Forward the old Gmail to the new address for a transition period.

From a hosting provider email

If you’re currently using email provided by your web hosting (common with cPanel-based hosts), you’ll need to export any existing mail before switching MX records. Most email clients (Outlook, Apple Mail, Thunderbird) support export to .mbox or .pst format, which can then be imported into Gmail.

From Microsoft 365

Google provides a migration tool in the Admin console (Data migration → Email) that can pull mail directly from an Exchange or Microsoft 365 account using IMAP. This preserves email history and folder structure during the move.

Checklist: getting set up

Week 1

[ ] Apply for Google for Nonprofits (if eligible)
[ ] Register or confirm your domain name
[ ] Create Workspace account and verify domain
[ ] Update MX records
[ ] Create admin account with 2FA

Week 2

[ ] Create user accounts for staff and key volunteers
[ ] Set up Google Groups for shared inboxes
[ ] Configure SPF, DKIM, and DMARC
[ ] Set up Shared Drives with folder structure
[ ] Migrate existing email if needed

Week 3

[ ] Roll out to all users with a brief walkthrough
[ ] Set up team calendars and share appropriately
[ ] Create email signature template
[ ] Enforce 2FA organisation-wide
[ ] Document the offboarding process