Administering community content
You 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 IBM® Connections.
About this task
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.
You can use search to find private communities, but you must add the global administrator to the search-admin role of the Search application. Use the My Organization Communities view to find public and moderated communities.
Procedure
-
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-policy.xml contains the "admin" block of grant statements and is not commented out.
- Start the
wsadmin client by completing the following steps:
- Access and check out the Communities configuration
files:
- From the temporary directory to which you just checked out the IBM® Connections configuration files, open the communities-policy.xml file in a text editor.
- Ensure that 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 your changes to the communities-policy.xml file.
- Check in the updated file by using the following
wsadmin client command:
CommunitiesConfigService.checkInPolicyConfig("<working_directory>", "<cell_name>")
- To exit the wsadmin client, type exit at the prompt.
- Stop and restart the server that is hosting the Communities application.