Here’s a feature request to allow group owner to not be member of the group, as discussed in Group owners for managing group membership. Let me know if there’s more clarification required here. Thanks, @sam!
AI-generated summary
A feature request has been made to allow group owners to not be members of the group they manage, as discussed in Group owners for managing group membership. tobiaseigen explains that admins currently handle group membership manually, which is time-consuming and places them unnecessarily in sensitive workflows. They propose delegating group management to non-admin users (e.g., helpdesk staff) without granting them admin privileges or access to private content or user data. InspektorCluzo supports this, citing their use case: volunteer dispatchers who manage meal delivery workflows need to assign users to consumer and driver groups without being members themselves. This separation enables distinct workflows — site administration (handled by staff) and mission-focused operations (handled by non-staff roles) — creating a clearer, more secure hierarchy aligned with the site’s purpose. The feature would empower admins to delegate group ownership while maintaining control over permissions and access.
I would love to see that.
The reason why I really like the concept of this feature is that, for many sites, that are two workflows:
(1) the worfklow of administering the site membership processes
(2) the workflow of administering what the site is here for. For us, it is delivering meals.
It makes sense for staff to be responsible for (1). But (2) should be administrable with a different cadre. This feature essentially enables the site admins to create a hierarchy of connected roles that are focused on the workflow of whatever the mission of the site is.