Skip to main content

Show Community Create Button only to users with role "community-creator"

Table of Contents

Since the update to the new HCL Connections Community Card-Based Overview (Connections 6.0 CR4) I search for a way to hide the button “Create Community” from users without the role “Community-Creator”. This was always possible in the earlier versions of Connections, but the button was shown always since the update.

During the year I mostly forgot about it, but yesterday I opened a case with HCL Connections Support and got immediatly following answer:

There is a new gatekeeper flag, CATALOG_CARD_UPDATED, which was introduced in IC6.0CR5 to help enhance the community card based view. This will need to be set to false to address this issue. You can perform the below steps to address this.

(1) Login to the below Connections url as the user mapped to the admin role for the Common application.

You can check the user mapped to this role from WAS console, Apps > Common > Security role to user/group mapping > admin

https://<your_connections_server>/connections/config/highway.main.gatekeeper.tiles[]

(2) Locate the CATALOG_CARD_UPDATED setting and change it from true to false.

(3) Save the setting

(4) Restart the Communities application

To make it short, this works perfectly as described. Now the button is not visible for users without the community-creator role.

HCL is planning a technote on this, I will update the post and add the url when it is available. Thanks to HCL for the fast solution and that I’m allowed to publish it already.

Warning

Afaik changing settings in /connections/config should only be made after advice from Support. Other changes are unsupported.

Update from 2021-11-18
#

Please check Hiding the Create Community button 2nd for the latest updates on the usage of CATALOG_CARD_UPDATED.

Christoph Stoettner
Author
Christoph Stoettner
I work at Vegard IT GmbH as a senior consultant, focusing on collaboration software, Kubernetes, security, and automation. I primarily work with HCL Connections, WebSphere Application Server, Kubernetes, Ansible, Terraform, and Linux. My daily work occasionally leads to technical talks and blog articles, which I share here more or less regularly.

Related

Update on the Touchpoint workaround (Updated)

·429 words·3 mins
Some weeks ago I wrote about an workaround to prevent TDI from deleting the touchpoint status in HCL Connections. During some research on TDI I found Mapping fields manually in the HCL Connections documentations. This document describes how to add additional fields to the TDI synchronisation. On point 11 I found something new for me. You can add additional fields and then add the content with an Javascript function for example.