Every church has a farewell lunch for the youth pastor who's moving on, or a thank-you card for the volunteer who ran the website for eight years. What almost no church has is a list of every system that person could still log into the day after the cake is gone.
That gap is easy to miss. Usually nobody means any harm by it. But it's one of the most common ways ministry data ends up exposed. In the 2026 State of Church Technology report from Barna and Pushpay, 83% of church leaders said they had at least some concern about privacy and security. In our work, the biggest risk we find usually isn't a hacker. It's an old login that nobody remembered to close.
Why This Matters More Than It Seems
Church technology has settled into a familiar stack: a church management system, an online giving platform, livestreaming, social media, texting, email, and the website. Each one holds something sensitive, whether that's member addresses, children's check-in records, giving histories, or the voice of your church on social media.
People often pick up access to those systems informally. A volunteer gets the website password "just for Easter." A staff member sets up the church's Facebook page from their personal account. The worship leader becomes the only admin on the YouTube channel because they were the one who clicked "create."
Then they leave. Usually on good terms. And the keys leave with them.
We've seen churches locked out of their own YouTube channels and Facebook pages because the only admin moved to another state and stopped answering texts. We've also seen former volunteers still receiving every prayer request emailed through the contact form, two years after they stepped away. Neither happened out of bad intent. Both were avoidable.
Start With an Access Inventory
Before you can offboard anyone well, you need to know who has access to what. This doesn't need fancy software. A shared spreadsheet works fine, with one row per system and these columns:
- System: ChMS, giving platform, website, domain registrar, email, social accounts, livestream, texting service
- Owner: the church-controlled account that ultimately owns it
- Admins: every person with admin rights
- Other users: everyone with lower-level access
- Billing: whose card or account pays for it
The domain registrar row matters more than most churches realize. If the person who registered your domain in 2014 still controls it, they effectively control your website and your email. Make sure it sits under a church-owned account with at least two people who can log in.
Make Ownership Institutional, Not Personal
The single best change a church can make is to stop tying critical accounts to one person's personal email.
Create role-based addresses on your church domain, like web@yourchurch.org, media@yourchurch.org, or admin@yourchurch.org, and use those as the owner or recovery address for each system. People come and go, but the role address stays with the church.
On every platform that allows it, keep at least two admins, and make one of them a senior staff member or an elder rather than whoever happens to be most technical. Facebook, YouTube, Google Workspace, Planning Center, and most giving platforms all support this. When one admin leaves, the other can step in without a recovery process that takes weeks.
A shared password manager built for teams helps here too. Instead of passing passwords around by text, you share access to a vault and remove it with one click when someone moves on.
The Offboarding Checklist
When a staff member or key volunteer steps away, walk through this list within a week of their last day. Ideally do it with them, before they go.
- Transfer ownership first. Before you remove anyone, make sure they aren't the sole owner of anything. Move ownership of social pages, YouTube channels, shared drives, and documents to a church account.
- Remove admin rights from every system in your inventory: ChMS, giving, website, social, livestream, texting, and the domain registrar.
- Rotate shared passwords they knew, especially for the Wi-Fi network, the soundboard computer, and any account that couldn't be given per-person logins.
- Check forwarding rules. Contact forms, prayer request forms, and group inboxes often forward to individual addresses. Update them so sensitive messages reach the right person.
- Handle their church email. Rather than deleting it right away, set an auto-reply that points people to the right contact, and forward incoming mail to their successor for a season.
- Review payment methods. Check whether any subscriptions are billed to their personal card. If they are, move them before the card disappears and the service lapses on a Sunday morning.
- Collect devices and recover files. Get back church laptops, phones, and keys, and make sure any ministry files on personal drives are moved somewhere the church controls.
- Update your inventory so the next transition is easier.
The whole process usually takes an hour or two. Untangling a lost account later can take months.
Do It With Grace
There's a pastoral side to this that matters. Offboarding shouldn't feel like an accusation. The people who held these keys were usually the ones who cared enough to set things up in the first place.
We encourage churches to frame it as stewardship rather than suspicion. Something like: "You've carried a lot for us. Let's make sure the next person can carry it as well as you did." Most people are relieved to hand things off cleanly. Many will even help you document what they built.
It also helps to make offboarding routine. If every transition follows the same checklist, no one feels singled out. It's simply how your church cares for what it's been entrusted with.
A Fall Reset
October is a natural time to do this. Ministry calendars are resetting, new volunteers are stepping in, and year-end giving is about to put extra traffic on your giving platform. Spend one staff meeting walking through your access inventory. You'll almost certainly find a login or two that should have been closed a long time ago.
If you'd like help untangling who owns your church's website, domain, and digital accounts, or want a setup that survives the next staff transition, we'd be glad to walk through it with you. Let's talk.