Disable the ability to add members to a community 

You can disable the functionality that allows community owners to add members to a community on a deployment-wide basis, so that instead new members must always be invited to join a community.

Before you begin

To update configuration files, use the wsadmin client. See Starting the wsadmin client for details.

About this task

Disabling the ability to add members to a community means that community owners can no longer add people to a community without their consent. Instead, people must be invited to join a community, and they must accept the invitation to become a member. This functionality is useful when you want users in your organization to actively choose to become part of a community.

When you disable the functionality for adding members to a community, the Add Members button no longer displays on the Members page.


To disable the functionality for adding members to a community...

  1. From the dmgr host:

      cd $DMGR_PROFILE/bin
      ./wsadmin.sh -jython

      If prompted to specify a service to connect to, type 1 to pick the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file using a local file path, pick the node where the file is stored.

  2. Check out the Communities configuration files using the following command:

      CommunitiesConfigService.checkOutPolicyConfig("<working_directory>", "<cell_name>")


      • <working_directory> is the temporary working directory to which the configuration XML and XSD files are copied. The files are kept in this working directory while you make changes to them.

          Note: AIX and Linux only: The directory must grant write permissions or the command will not run successfully.

      • <cell_name> is the name of the WAS cell hosting the IBM Connections application. This argument is required. If you do not know the cell name, you can determine it by typing the following command in the wsadmin command processor:

          print AdminControl.getCell()

      For example:

      CommunitiesConfigService.checkOutPolicyConfig("/opt/my_temp_dir", "CommServerNode01Cell")

  • Navigate to the working directory that you specified in the previous step and open the communities-policy.xml file using a text editor.

  • Comment out or remove the add.others action for each community type from the following section of code:

  • Save your changes and then close the communities-policy.xml file.

  • Check in the updated policy file using the following command:

  • Synchronize your changes across all nodes and then restart the Communities application.

    Parent topic

    Manage membership in Communities