---
title: One Person Has All Your Church's Passwords (And That's a Leadership Problem)
description: When one staff member holds every password, you don't have a system—you have a single point of failure. Here's how to fix it before Sunday breaks.
---

[Church Leadership | Chemistry Staffing](https://blog.chemistrystaffing.com)

# [One Person Has All Your Church's Passwords (And That's a Leadership Problem)](https://blog.chemistrystaffing.com/one-person-has-all-your-church-s-passwords-and-that-s-a-leadership-problem)

 Written by [Todd Rhoades](https://blog.chemistrystaffing.com/author/todd-rhoades) | Oct 12, 2026, 5:00:00 AM

It's Sunday morning. The livestream laptop won't unlock. Planning Center was working perfectly yesterday, but now it won't open. The resource room code died sometime last month, and the one person who knows all of it texted in this morning—she's sick.

🎧 Listen to this episode:

People are frantic because they can't get ahold of her, and they can't get into any of the programs. Sound familiar?

If you've ever experienced this particular brand of Sunday morning panic, you're not alone. This scenario plays out in churches every single week across the country. But here's the thing: **this isn't a technology problem. It's a leadership problem that just happens to have a password on it.**

## She Has Every Login (And You Let It Happen)

Let's talk about her for a minute. She has the login information for Planning Center. She has access to the Facebook page. She knows the door codes, the giving kiosk password, how to unlock the streaming laptop, and the administrative password for the Wi-Fi that actually works.

She might be your kids director. She might be your office manager or your part-time communications person. Here's what she's definitely not: hired specifically to be your IT department.

You didn't set out to make her the keeper of all knowledge. You handed her the next login because she answered the last question. She was "so good with tech," so you kept coming back. And now? She's become the building's memory. Everything you need to function lives in her head, and she's just one fever away from a very quiet, very locked-down Sunday morning.

> **Proverbs 21:5 (NIV)**  
> "The plans of the diligent lead to profit as surely as haste leads to poverty."
> 
> Careful planning and documentation in our ministries prevents chaos and honors the resources God has given us.

## You Called It "Helpful" (But Really You Built a Trap)

Here's the sentence that's doing way too much work in your church: "She's so good with tech."

That one sentence means you don't have a list. It means you don't have a backup. It means you have no idea what she's actually holding in her head until something breaks and she's not there to fix it.

When she takes a Tuesday off, three people text her anyway. When she's on vacation, you still call. You tell yourself she doesn't mind. But let me tell you something: **she minds.** She just can't say it without sounding unhelpful.

Think about that for a second. The same trait you praise her for—being so helpful, so willing, so good with all of this—is actually the trap you've built for her. You've made her indispensable, and that's not the gift you think it is. It's a burden she can't put down because you haven't given her permission to share it.

I had a conversation just last week with someone who left their church two months ago. They got a call from the church asking for a password—not even a church account password, but their *personal* password because they couldn't get into a laptop any other way. Two months later, and the church still didn't have a system.

That's not on the person who left. That's on the church and its leaders.

## I Know Why It Happened

Listen, I know your heart. You weren't trying to create a liability. You weren't hiding the keys. You were keeping the service running. Someone had to reset the router. Someone had to know the code. She said yes. That's decent. That's helpful.

It's also how a church ends up with one person holding the whole building in their head.

**Helpful is not a system.** Helpful is a person you will someday lose. And when you lose her—whether to another job, burnout, vacation, or illness—you're going to find out exactly what was never written down.

You can still love her. You can still appreciate everything she does. But you cannot keep using this as your plan. A password living in one brain is not stewardship. It's a bet that she'll never get the flu, never go on vacation, and never decide that she's done being the only one who knows how things work.

> **Ecclesiastes 4:9-10 (NIV)**  
> "Two are better than one, because they have a good return for their labor: If either of them falls down, one can help the other up. But pity anyone who falls and has no one to help them up."
> 
> Shared knowledge and cross-training means we're never dependent on just one person—we truly work as a team.

## Ask Yourself This Question Right Now

Where do your logins live?

If the answer is "in her head" or "in his head," you don't have a system. You have a person. And that's not the same thing.

If she left Friday, who opens Planning Center on Sunday? Who changes the door code after a volunteer quits? Who can get into the giving software when the kiosk freezes?

If you don't know—or if you know it's one person and it's not written down anywhere—that's not a tech problem. **That's a leadership problem with a password on it.**

We talk a lot about having a termination file—that folder with all the important information you need when someone leaves. This is the other side of that. You kept every access point with the person you trust most, but trust is not a backup plan.

I've seen situations where something tragic happens—a death, a sudden conflict, a relationship breakdown—and suddenly the person who held all the passwords isn't your friend anymore. They're not available anymore. And then you're really vulnerable, because they effectively own all your systems.

## Two People. One List. This Week.

Here's what I want you to do, and I want you to do it this week. Not after Thanksgiving. Not after Christmas. This week.

Sit down with the person who has all the passwords. Bring a notepad or open a document on your laptop. Write down every single login she's got in her head. Door codes too. That laptop that only she can wake up. Everything.

Then name a second person. Not "the staff" in general. An actual name. Someone who needs to have access to this information, or at least needs to know where it lives.

Put the list somewhere secure where those two people can reach it:

- A locked drawer in your office
- A safe with a combination that multiple people know
- A password manager that the church pays for (like 1Password or LastPass)
- **Not** a sticky note in the copy room
- **Not** a random document on someone's personal computer

Then—and this is important—tell her she can stop being the building. If you present this right, this is a gift to her. You're not taking away her value; you're giving her permission to take a day off without her phone buzzing every twenty minutes.

### Action Steps You Can Take Today

- **Conduct a "what if" audit:** Ask each staff member to list 3-5 critical things that only they know how to do.
- **Schedule the password meeting:** Put time on the calendar this week to sit down and create the master list.
- **Research password managers:** Look into tools like 1Password, LastPass for Teams, or other secure solutions.
- **Name your backup:** Identify the second person who needs access to critical information in each ministry area.
- **Create a simple SOP template:** Give your team a standard format for documenting processes and procedures.

## One Staffer Holding Everything Isn't a Gift

Let me be really clear about something: when one person holds every password, every process, every piece of critical knowledge in their head, that's not a spiritual gift. That's not them being extra helpful or particularly valuable.

It's a single point of failure that you keep calling "helpful."

And every Sunday morning that goes smoothly because she's there is actually evidence that you're one sick day away from chaos. The system is working—until it suddenly isn't.

> **1 Corinthians 14:33, 40 (NIV)**  
> "For God is not a God of disorder but of peace... But everything should be done in a fitting and orderly way."
> 
> Creating order through documentation and systems reflects God's character and creates peace for our teams.

## The Sunday You Actually Want

I know this feels uncomfortable. It feels like you're taking something away from the person who has been saving you week after week. But what you're actually doing is creating a church that can function even when she has the flu.

You're building a ministry that doesn't rest entirely on one person's shoulders. You're creating space for people to actually take time off without their phone being blown up with emergency texts. You're being a good steward of the resources and people God has given you.

That's the Sunday you actually want. The one where things work even when someone's sick. Where you can call a substitute because the systems are documented and the passwords are accessible. Where "helpful" doesn't mean "the only person who knows anything."

So make the list this week. Name the backup. Put it where two people can reach it. This week.

Because if you won't make the list, you've already named the plan: she holds it, and you hope she never stays home.

### Take the Next Step

**What's one password, process, or piece of critical information you've been keeping in your head that needs to be documented?** I'd love to hear how you're working through this in your church context. Email me your thoughts at [podcast@chemistrystaffing.com](mailto:podcast@chemistrystaffing.com).

And if this helped you think differently about your systems, share it with another church leader who needs to hear it. Let's help each other build healthier, more sustainable teams.

[View full post](https://blog.chemistrystaffing.com/one-person-has-all-your-church-s-passwords-and-that-s-a-leadership-problem)

```json
{
  "@context" : "http://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Todd Rhoades"
  },
  "dateModified" : "2026-10-13T13:47:45.691Z",
  "datePublished" : "2026-10-12T05:00:00Z",
  "headline" : "One Person Has All Your Church's Passwords (And That's a Leadership Problem)",
  "image" : {
    "@type" : "ImageObject",
    "height" : 768,
    "url" : "https://5045578.fs1.hubspotusercontent-na1.net/hubfs/5045578/blog-images/featured/featured_212.png",
    "width" : 1376
  },
  "mainEntityOfPage" : "https://blog.chemistrystaffing.com/one-person-has-all-your-church-s-passwords-and-that-s-a-leadership-problem",
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "height" : 60,
      "url" : "/hs/hsstatic/content_shared_assets/static-1.4092/img/default-amp-logo.png",
      "width" : 60
    },
    "name" : "Church Chemistry"
  }
}
```