群主不一定是群成员

On my site I have a use case for people being given the privilege of managing group membership without being a member of the group themselves. I assumed this is how it worked and was surprised to see that someone I added as group manager is now also a group member.

The use case? We use groups to assign badges. And to give access to private categories. And the people responsible for doing this are not always group members.

Edit: having noticed this, I then removed some group owners only to realize they are still group members. Seems to me these should be managed independently.

15 个赞

We ran into this problem this week, too. (Although our groups represent a “group” membership outside of Discourse, too.) But that membership is not decided by a member of the group, and not by a Discourse admin, either.

5 个赞

Just ran into this very problem, where a group’s membership is not administered by a member of the group.

Our use case

We want a handful of non-Discourse-admins to be able to manage group membership for several groups without becoming members of those groups themselves.

Extra credit

This is probably asking too much, but I thought I’d throw it in… it’d be awesome if a group could be named as admin of another group (i.e., membership of the @bar group can be managed by any member of the @foo group). This would allow us to have a “group managers” group containing our non-Discourse-admins in charge of managing other groups’ memberships. :slightly_smiling:

5 个赞

I just moved this to the #feature:voting category as I’d like it to be thrown into the mix for voting when that starts happening.

I like this idea! There is one person in charge of managing internal groups in my community but does not need to have admin privileges. It would be helpful to be able to set up a group for this so we can easily add/remove people to help her.

Another related feature that would be needed is the ability for group owners to see and manage the group even when “Group is visible to all users” is deselected. There should also be the option to allow group members, or members of a specific other group, to see the group.

1 个赞

Sure, I am open to disconnecting the two permissions.

7 个赞

Any chance the goal of “group owner does not need to be group member” with stretch goal of “group can be named as owner of another group” would be suitable for a GSoC project?

2 个赞

Very unlikely, way too small of a job.

Group can be owner of another group is not even something I would be comfortable adding.

Did anything come from the OPs request to separate group membership & group ownership? @sam supported the idea a while back (above).

Scenario: We added a moderator to a group, to manage group membership. However, this resulted in him getting the group’s badge displayed on his avatar.

3 个赞

Thanks for the reply, @Biscuit! I just came across this again in my community and the issue persists. In fact, it’s becoming a bit of a problem because certain leaders in my community complain that they are not trusted to properly manage the groups they are charged with managing. They have to ask an admin to add/remove people. I’m trying to keep down the number of admins (a conversation for another day).

It’s pr-welcome so the discourse team have indicated they are open to having it done as a community contribution. Any takers?

It appears to me that with the new front-end groups management interface, there is no obvious place to list owners who are not members. Perhaps the answer is simply to just list them at the top, with the Owner badge but not the date added, posted or seen. And/or to list with a highlight color, as on staff posts?

Then the functionality to add owners could be a + ADD OWNERS button next to the existing + ADD MEMBERS button. Selecting this would pop up a modal to add one or more owners. On the list, if the REMOVE MEMBER button is selected and the member is an owner, the user would remain on the list as an owner but not as a member. If REMOVE AS OWNER is selected, the user would remain as a member but no longer as an owner (unless the user is not already a member and was only listed as an owner, in which case the user would be removed from the list entirely).

Unannotated screenshot for illustration.

5 个赞

We have the use case that there should be one master group that manages many smaller groups (~30 / i.e. @Archangels manage local Angel communities). They should not have to be members of all 30 groups, just be able to add/remove members.

3 个赞

We also run into this each time Google Summer of Code comes around. It also seems related to the various ideas about hierarchical/sub-groups, too.

3 个赞

是的,您好,我也遇到了同样的问题,我将举一个它提出的问题示例,这有点令人烦恼。作为群组的创建者和所有者,必须有一个默认的群组管理员,那就是我,管理员,我不能指定其他人。因为没有理由让那个人管理我亲自创建的群组。应该有群组成员和群组管理员,但管理员不一定非得是该群组的成员。以下是这种情况给我带来的问题。

我使用了expert category插件。因此,我将某些类别分配给了一组专家。不幸的是,我被自动视为该群组的专家,这非常不好,因为当我发布新主题时,它会显示我作为专家贡献,而我根本不是该群组主题的专家。嗯,我不知道我是否表达清楚了。 :grin:

嗨 Patrick!虽然我仍然认为这个功能请求是合理的,但我不确定我是否理解你的用例。

专家类别插件是否需要群组所有者?否则可以创建没有所有者的群组。

您需要为允许用户请求加入群组的功能设置群组所有者。

我认为这很有意义,因为用户需要请求才能成为成员,而不是自己决定自己是专家。您是否也对 @support-explorers 群组做了类似的事情?

@patrickemin 我去年报告了一个 bug,可以帮助您避免被添加为群组成员。但您需要找到一种工作流程,以便您经常检查群组的请求选项卡中是否有新请求,因为在这种情况下您不会收到消息。
但启用成员资格请求后,您可以将自己从群组中移除:

4 个赞

感谢 @moin!我对您在 Discourse 方面的知识渊博程度感到印象深刻。:clap:

我只是在思考为什么需要群组所有者才能启用“允许用户发送成员资格请求”设置,这对我来说很有意义。您不希望在有人请求加入群组时必须通知所有版主。所以是的,在这种情况下,您也希望群组所有者不必是群组成员。

4 个赞

依我看,一个相当简单的解决方案是,加入群组的请求不仅发送给群组所有者(如果存在的话),也发送给管理员。这样一来,即使没有群组所有者,管理员也会收到通知,并且不必成为群组所有者或群组成员。

一个不错的选择是允许添加一个组作为所有者。这将允许具有层次结构的层级组,而不是只有所有者/成员,你知道通过添加一个组作为所有者——管理员、所有者和成员。但有一个注意事项,可能会继承托管组的类别/访问权限,因为它们在技术上属于两个组。

我想探索“批量添加所有者”,也许机构会觉得它很有用。

回顾这个话题,不禁注意到选择一个组进行批量添加可能不是最好的;

也许如果它被同步了会很糟糕,而且可能很难区分原因和结果。

Well we already have a group owner if sorts with Category moderators. I do something like this manually.

Being able to have a group manage a group means easier to add/remove owners without an admin being required As the Group Owners Group has it’s own core owners that can add remove regular members in the owner group.

感谢 Dan — 你关于类别版主能够拥有与其类别相关联的群组的观点确实引起了我的共鸣。你似乎设想了一个更灵活的管理结构,其中一个群组可以管理另一个群组 — 这将大大简化权限和工作流程。

目前,Discourse 只允许单个用户成为群组所有者。但在实际用例中,尤其是结构化社区(如学校、部门或团队),我们经常希望能够说:

  • “群组 A(例如 mentor-coordinators)可以管理群组 B(例如 mentors)”
  • …而无需将 A 的成员添加到 B 或继承其徽章/身份

这将允许:

  • 身份(群组成员资格)和控制(群组所有权)之间进行清晰分离
  • 在不授予全站管理员或版主访问权限的情况下,委派成员资格管理(邀请/移除/批准)
  • 能够将类别的版主与控制其发帖群组的群组相关联

听起来你指向的是一个群组所有权不仅接受用户名,还接受其他群组的模型。这个想法与几个较早的帖子一致:

我很想知道你会如何设想这个功能:

  • 如果我属于管理群组,用户界面会显示所有权继承吗?
  • 群组所有者是否可以编辑所有群组设置,还是只能管理成员?
  • 这可以与类别权限配对,或者自动链接到群组的类别吗?

绝对支持这个想法 — 希望看到它得到进一步发展。

2 个赞