Finding Your People: The Member Directory That Actually Works for Campus Groups

Why a simple contact list isn't enough for campus groups

Most church and community apps treat the member directory like a photocopied list you'd tape to a noticeboard. Name. Email. Done.

But campus groups are different. A Bible study coordinator needs to know who's active in their specific group. A prayer request board moderator needs to contact members who've posted without public replies. Someone new to campus needs to find the chaplain's contact, not the 80-person group chat.

When we started building Campus Fellowship, we spent weeks watching how student-led groups actually worked. We saw groups use spreadsheets, scattered WhatsApp contacts, and the unfortunate 'just ask around' method. Nobody had visibility. People felt invisible.

The directory we built reflects that reality. It's not about having everyone's number. It's about having the right information for the right moment.

How privacy and choice actually work in practice

The first rule we set: nobody gets listed without choosing to be. When a member joins a campus group through the app, they see a simple question during sign-up. 'Can other members see your profile in the directory?' Yes or no.

Some students say no immediately. They're not ready, or they prefer privacy. That's fine. They stay invisible. Others choose to appear but limit what shows. You might see their name and their group involvement, but not their phone number. Or vice versa.

We learned this matters because campus feels different from a Sunday parish. You're 18, maybe away from home, still figuring things out. A member directory that forces transparency breaks trust. One that respects choice builds it.

For group leaders, there's still a full roster view. You need to know your people. But even that respects what members have chosen to share. If someone's opted out of public visibility, the leader still sees them in admin view, but can't export their number without a good reason.

The moments when people actually use it

This is where it gets interesting. We've watched how campus groups use the directory, and it rarely matches the pitch we'd prepared.

A new student arrives in September. They find the CU on the Campus Fellowship app. They see a prayer group meeting Wednesday evenings. They want to know if it's friendly, if anyone their age goes, if the person leading it is approachable. They tap the prayer group, see the coordinator's name and bio, and suddenly it feels less scary.

A Bible study leader is running a group on Romans. Someone posts a question on the community board that would work perfectly for that study. The leader can contact them directly through the app, invite them, without asking for their number first.

A member has been quiet for three weeks. Their group leader notices and wants to check in. They can see that this person is still technically part of the community, but they've missed the last few events. A quick message through the app: 'Haven't seen you in a bit, everything okay?'

These aren't flashy moments. They're the everyday work of keeping a community together.

What happens when your group grows past a certain size

We built Campus Fellowship for both student-led fellowships and larger campus ministries. The directory scales differently depending on which one you are.

If you're running a small student-led prayer group with 15 people, the directory is just a list. Everybody's name, maybe their year of study, which groups they're part of. You probably know them all anyway.

If you're a campus ministry running four different groups across multiple years, the directory becomes your operational tool. You can filter by group. See who's active and who's gone quiet. Find the person who said they'd help with events but you've lost their number. The chaplain can see every member across every group, with full contact information if they've chosen to share it, without everyone seeing everyone else's data.

For larger organisations on the premium tier, we've added permissions. A Bible study coordinator only sees their own group's directory, not the whole campus ministry. A prayer request moderator can see who's posted but not browse the full member list. It stops information overload and respects boundaries.

The thing we almost got wrong

During our first beta with a Cambridge CU, we gave leaders the ability to bulk-export member lists as spreadsheets. It seemed useful. It was a disaster.

One chaplain exported the list, shared it with a volunteer coordinator outside the app, and a few contacts leaked into a general student mailing list. Nothing malicious. Just careless. Three students asked us to remove them entirely.

We cut the export feature. Now, if a leader needs to contact their group, they do it through the app. It's slower. But it's contained. It's trackable. And members know that their information isn't leaving the system they chose to join.

That decision probably cost us some functionality adoption. We accepted that trade-off. On campus, trust has to come first.

The directory is part of something bigger

The member directory doesn't stand alone. It connects to the prayer request board, where members post needs and others can reach out. It connects to the event calendar, so you can see who's actually attending. It connects to group pages, where the Bible study coordinator lists their members and upcoming sessions.

A student new to campus sees the directory and realises: these aren't just names in a list. These are the people running the prayer group they're interested in. These are the other members already part of it. This is a real community, not a digital mirage.

That's what we were actually trying to solve.