Mapping a community page to a community
Map a community page to an IBM Connections community so the portlets can interact with community content.
Follow the steps to map the community pages to a community based on what WebSphere Portal Server we are using.
- To map community pages to a community on a WebSphere Portal 8.5 server, follow the steps in the article Manage community associations in the WebSphere Portal Knowledge Center
- Assign access to the page. If the community has restricted membership, we can secure the page so that only members of the community can see the page in the Portal navigation. We can also access assign on community pages mapped to public or moderated communities, but doing so does not restrict access to the content in the community. There are other mechanisms, including APIs, mobile clients, connectors and search and portlets on other pages which may expose the content outside the community page. Membership lists in Connections communities should have the correct level of access to community content and Portal pages should reflect that level . Before you use communities for access control on pages, follow the steps in Integrate community membership with Portal security.
- Navigate to Administration > Manage Pages and find the community page for which to set access.
- Click Set Page Permission (lock icon).
- Uncheck Allow Inheritance for all rows and click Apply.
- Click on the Edit Role button in the Privileged User and User columns and make sure no users or groups are added that you do not want to access this page.
- Click on the Edit Role button in the Privileged User or User column, depending on what level of access to grant to community members. See the Roles.for a description of roles in WebSphere Portal.
- Click Add.
- Change Search by to displayName.
- Name of the community in the search box and click Search.
- Check the box next to the group representing the community and click OK. If successful, the group appears in the list of members in the role and a message indicates the members were successfully added to the role.
- Before adding portlets to the community page, verify the corresponding widget exists in the community. For example, before add a Blogs portlet to the community page, verify the Connections community contains a blog. If not, add the Blogs widget to the Connections community using the browser interface.
What to do next
If the portal administrator configures a portlet with a new connections server URL for a community page, then the changes will take effect only after the community page is configured with a valid community ID for the new connections server, by editing the portal page parameters settings to include the new community ID.
Parent topic:
Community Pages
Related: