Mapping a community page to a community | HCL Digital Experience
Map a community page to an HCL Connections community so the portlets can interact with community content.
Before you begin
About this task
Follow the steps to map the community pages to a community based on what HCL Digital Experience server you are using.
Procedure
- To map community pages to a community on HCL Digital Experience 8.5 server, follow the steps in the article Managing community associations at HCL Software Support.
-
Assign access to the page.
If the community restricts membership, you can secure the page so that only members of the community can see the page in the Portal navigation. You can access assign on community pages that are 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 might show the content outside the community page. Membership lists in HCL Connections communities must have the correct level of access to community content and Portal pages must reflect that level. Before you use communities for access control on pages, follow the steps in Integrating community membership with Portal security.
-
Before you add portlets to your community page, make sure that the corresponding widget exists
in the community.
For example, before you add a Blogs portlet to the community page, make sure that the HCL Connections community contains a blog. If not, add the Blogs widget to the HCL Connections community by using the browser interface.
What to do next
Note: If the portal administrator configures a portlet with a new connections server URL for a
community page, the changes take effect only after the community page is configured with a valid
community ID for the new connections server. The community ID is configured by editing the portal
page parameters settings to include the new community ID.