Welcome to the Connections Product Ideas Lab! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by the Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events, please visit our Connections page.


Add new J2EE security role "privileged-community-creator" for Communities app

Add a dedicated role named "privileged-community-creator"  which can be used to assign the          
permission to create private communities only.

 

In the current implementation using community policy, you can restrict the community types which users in the role "community-owner" are allowed to create (https://www.ibm.com/support/knowledgecenter/en/SSYGQH_6.0.0/admin/admin/t_admin_communities_prevent_user_creation.html). For example, you can limit the types to "public" and "publicInviteOnly".

Users have to be assigned to J2EE role "admin" to be able to create all types of communities including "private". However, being assigned to J2EE role "admin" includes other (unwanted) privileges.

Having a dedicted J2EE role "privileged-community-creator", you could easily assign the permission to create private communities to a group without assigning all administrative privileges.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Sep 21 2018
  • Under review
  • Attach files