Groups & Community

Group roles and what each one can do

August 8, 20263 min readBy Chris Ikhiede

Everyone in a group holds a role. Two of them carry real permissions; two are descriptions. Knowing which is which saves you from assuming someone can do something they can't — or from handing out access you didn't mean to.

Who this is for

Administrators and group leaders deciding who runs what.

The four roles

RoleCan see the group's membersCan message the groupCan approve join requests
LeaderYesYesYes
Co-leaderYesYesYes
FacilitatorNo more than a memberNoNo
MemberNoNoNo

Leader and co-leader are the same in what they can do. The difference is descriptive: one person is the leader, and co-leaders share the running of it.

Facilitator carries no extra permissions. It's a label for your own organisation — the person who hosts, or leads the discussion, or brings the food. Useful for keeping track of who does what, but it grants nothing. If you want someone to be able to message the group or approve requests, make them a co-leader.

That distinction matters, so it's worth being blunt about it: naming someone a facilitator and expecting them to handle join requests will leave those requests sitting unanswered.

One leader, several co-leaders

A group has a single leader. Naming a new one moves the previous leader to an ordinary member — so if they're staying involved, set them as a co-leader afterwards.

There's no limit on co-leaders. For a group run by a couple, or one with a rota of hosts, making them all co-leaders is the straightforward answer.

Staff access, separately

Beyond group roles, three church roles reach every group: Super Admin, Admin, and Groups. Someone holding one of those can see and manage any group, whether or not they're a member of it.

This is why the Groups role is the right one to give a groups pastor or coordinator. It gives them everything they need across all groups without making them a full Admin, which would also hand them finance, giving, and every member record.

The People role is about the member directory, not groups. People staff can put a person into groups while adding or editing them, but they do not see the Groups page unless they also lead a group.

If someone should run only their own group and see no others, such as a choir director or a home group leader, they need no church role at all. Making them Leader or Co-Leader of the group is enough: on the web they then see and manage only the groups they lead. See "How do I let a group leader see only their own group?".

Changing someone's role

Open the group's member list and change the role there. It takes effect immediately.

Worth doing when a group changes hands. The most common problem isn't the new leader being missed — it's the old one never being removed, so a group ends up with people who can message everyone in it long after they stopped running it.

What a leader cannot do

A group leader's access stops at their group. Being leader of the Tuesday men's group gives no visibility into any other group, and no access to church-wide member records, giving, or settings.

That's the design: it lets you give real responsibility to volunteers without giving away the church's data.

You'll know it worked when…

The person shows against the right role in the group's member list, and a new co-leader can see the members and message them.

If something goes wrong

  • A co-leader can't message the group — check the role saved as co-leader rather than facilitator or member.
  • The previous leader lost their access — that's expected. Naming a new leader moves the old one to member. Set them as co-leader if they're staying on.
  • Someone can see groups they aren't in — they hold Super Admin, Admin, or the Groups role. That's church-wide access, not group access.

Related articles

  • Creating a group
  • How people join a group
  • Recording group attendance

Was this article helpful?

Back to Knowledge Base