Delegate Group Admin permissions to manage membership and group home page

Hi @Marion Frecaut - this is a feature I’m itching for because, as part of our gamification structure, we want to offer people who reach our higher ranks in the Community the chance to start a group. I want it to be their group, not ours, and give them the tools they need to grow it in line with their own vision.

Salesforce has this capability and I used it extensively in a previous community.

1. Create group and edit group details - yes
2. Add, invite, approve users to join the group - yes
3. Create events for group members - yes
4. Highlight topics or external content on the group detail page - yes
5. Notify members of groups of news by email - yes, and this is just needed for the community as a whole!
6. @mention groups members in topics (in the way I mention @Marion Frecaut , I would mention @Groupmembers) - YES
7. Anything else? - As a community manager, I need an audit log of what group owners have been up to

Order of importance = 1,2,7,5,6,3,4

Very much agreed on this feature.  Is there a possible timeline when this will be possible? Our community is over 30k and managing all the groups for that many individuals will not be feasible.  Please help😍

Hi @andre.gerard unfortunately there is no timeline I can communicate to you about when this idea will be delivered. This is still a interesting idea to us and we are monitoring it closely. 

I will keep checking-in @Marion Frecaut !

Having this feature is super business critical for us. It is really necessary to be able to allow other users the right to operate groups without them being admins. Ideally, it would be great to have this option as a custom role that we could delegate to employees. It is really important for internal adoption and the success of our Community that other employees can participate in the Community independent of admin help or assistance, otherwise it creates real frustration. Please look into finding a solution for this ASAP! 

Hi @Marion Frecaut - as mentioned with your team members this request is critical for us. Couldn’t agree more with @JKelley & @ruth.kenrick on groups management, and I would add the right to edit event for non-seat members.

First thing, from my experience with community platforms, it has never been a requirement to be in an admin seat to edit groups or events. We’ve just got started with InSided and this is definitely a setback… I can fully understand that the creation of groups or events can rely on admins only but edition really limits the use-cases.

Second, it create a real adoption issue for internal users as no one else that admins can feel responsibilized. Having to manage all group admissions, editions or all events editions (we post replays in the event description after our events - very simple task but we would love to have the owner of the event to it, put his/her tone of voice in the description, etc.), is a real pain and does not let employees feel actively part of the community. 

This issue potentially limits the usage of +200 internal experts who could help admins in making the community thrive and grow, especially when having a group oriented adoption strategy. 

Third, it just makes the community a lot “harder” to manage and does not let admins focus on more important tasks.

This role should be accessible to super users (as a reward for engagement) and employees with limited access to Control. 

1. Yes
2. Yes
3. Yes
4. Yes
5. Yes
6. Yes
7. I would add have access to the event edition part. 

Order of importance: 2, 4, 6, 7, 3, 5, 1

Please reach out if you need any details! Happy to help on this one.

Just adding this is becoming more and more useful for us to have as well - confidence isn’t high given this is a year old 😬

@Julian ref our conversations on this over the past months: this would be super valuable and is a bottleneck for engagement. 

For us: the most important feature here would be for all our product-managers to themselves (with custom role from the front end?) be able to update the ideation status in Product Ideas. The product managers are the only ones that would know the true status to each idea. 

• Who should get this role? ( End users, super users or/and employees with limited access to Control...) Everyone. Our community members, community managers, admins, moderators…

Which of the below actions would you say a they should do:

1. Create group and edit group details. I would prefer for team members (admins, community managers, moderators) to have this permission and then for it to be an option for the admin to decide whether or not community members can do so.
2. Add, invite, approve users to join the group. Once you are the group manager, anyone should have this permission.
3. Create events for group members. Once you are the group manager, anyone should have this permission.
4. Highlight topics or external content on the group detail page. Once you are the group manager, anyone should have this permission.
5. Notify members of groups of news by email. Yes… but if team members (admins, community managers, moderators) can view the content and analytics for those.
6. @mention groups members in topics (in the way I mention @Marion Frecaut , I would mention @Groupmembers) No. Anywhere I have seen this done has been a nightmare of notifications for members. 
7. Anything else? Multiple group owners/admins. 

• Of these actions, which ones are the most important that they have. Feel free to order them from most important to least important. 
  • 2, 7, 4, 3, 1