Welcome to the HCL 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 HCL 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 HCL Connections page.
As the reader and person role are not working the way I would understand the documentation, I think there are several possible scenarios needing read-only access for all users or special groups.
So I would expect a user group which is enabled for J2EE role 'reader', but no other role, in an application, can read public content, or content they are a member of, but can't create posts, documents or entries. At least in Activities, Forums, Profiles and Homepage removing a group from
person, removes also the access to the start page of the application.During security incidents, it would also be helpful to start the environment read-only for everyone to have access to documentations (Wikis), but prevent changes.