Administer community content

We can create a dedicated administrator with access to all communities, public, or restricted. This administrator has granular control over communities content, including the ability to edit or remove inappropriate content. This administrator is also required for IBM Lotus Sametime integration with Connections.

Global communities administrators can access all communities with rights to view and update community settings, members, invitations, bookmarks, and feeds. However, within restricted communities the global administrator cannot view and manage remote widget applications, such as Activities or Wikis. To manage content in remote widget applications, you add the communities global administrator to the Java EE admin role for all of these applications. See Assigning people to Java EE roles for detailed information. Once logged in, the communities global administrator is in the admin role and can manage content in any of them, whether the applications are stand-alone or remote widgets in a community.

We can use search to find private communities, but add the global administrator to the search-admin role of the Search application. Use the Public Communities view to find public and moderated communities.

The global administrator role is not supported on mobile devices. Global administrators must use a supported browser.

1. Create a user who is dedicated to administering content, and add them to the Java EE admin role of Communities, Activities, Blogs, Files, Forums, and Wikis. Also, add them to the search-admin role of Search. See Roles. In the following steps, ensure that communities-config.xml contains the "admin" block of grant statements and is not commented out.

2. Access the Communities configuration files:
   cd app_server_root/profiles/Dmgr01/bin
   ./wsadmin.sh -lang jython -user admin_user_id -password admin_password -port SOAP_CONNECTOR_ADDRESS_PORT
   execfile("communitiesAdmin.py")
   CommunitiesConfigService.checkOutPolicyConfig("/tmp", "cell_name")

   To get cell name...

   print AdminControl.getCell()

From the temporary directory to which you just checked out the Connections configuration files, open the communities-policy.xml file in a text editor.

Ensure the file contains the following grant statement, and that it is not "commented out" (disabled).

<comm:grant>
 <comm:principal class="com.ibm.tango.auth.principal.Role" name="admin" />
 <comm:permission class="com.ibm.tango.auth.permission.CommunityManagementPermission" communityType="*" action="*" />
 <comm:permission class="com.ibm.tango.auth.permission.CommunityMembershipPermission" communityType="*" action="*" />
 <comm:permission class="com.ibm.tango.auth.permission.CommunityAccessPermission" communityType="*" action="*" />
 <comm:permission class="com.ibm.tango.auth.permission.CommunityReferencePermission" communityType="*" action="*" />
 <comm:permission class="com.ibm.tango.auth.permission.CommunityBroadcastPermission" communityType="*" action="*" />
 <comm:permission class="com.ibm.tango.auth.permission.CommunityInvitePermission" communityType="*" action="*" />
</comm:grant>

Save the changes to the communities-policy.xml file.

Check in the updated file by :

CommunitiesConfigService.checkInPolicyConfig("</tmp>", "<cell_name>")

To exit the wsadmin client, type exit at the prompt.

Stop and restart the server hosting the Communities application.

Results

When logged in to Communities, the global administrator specified in the various Java EE roles should be able to view and edit all communities and community resources.

Parent topic:
Administer application content

Related:

Remove unwanted community content

Related:

Add owners and members to a community

Assigning people to Java EE roles

Related reference:

Administer application content