+

Search Tips   |   Advanced Search

Community associations


We can create, view, modify, or delete community associations on a page with...


Create a community association

  1. Create a community association in the user interface with the Associations window using one of the following options.

    • Open the Associations window from the site toolbar.

      1. Edit the page for the community association and click....

        If an association exists, it is displayed. The Community section is displayed only if an IBM Connections server is configured for the portal.

    • Open the Associations window from the page properties portlet, and click...

        Administration | Portal User Interface | Manage Pages | page_name | Edit properties icon | Advanced | I want to edit page associations | Communities tab

      If an association exists, it is displayed. The Community tab is displayed only if an IBM Connectionsserver is configured.

  2. Create the association. We can create an association with one of the following methods:

    • Click Select Community.

      The portal queries the IBM Connectionsserver and lists available communities. Select the community to associate with the page.

      Depending on the number of available communities, only a subset of all communities might be listed. If the IBM Connectionsserver is not running, no communities are listed.

      We can filter the list of communities by entering text in the Find Community field. The list of communities is narrowed to only those communitiecontaining the search text in the community title.

    • To associate the page with the same community associated with the parent page, click...

        Use community_name from parent page

  3. To automatically grant page access to members of the associated community, click...

      Restrict view access to this page to community members

    Activating this feature results in the following changes:

    • The User role is assigned to the virtual user group that represents the community and the page. This access is in addition to any access that you explicitly grant to the page.

    • Role blocks are defined for the page for the User role and the Privileged User role. These role blocks prevent corresponding access privileges that are granted to the parent page from being propagated to this page.

    This setting is displayed only if you have installed and enabled the IBM Connections adapter for VMM users and groups.

    Access control changes from this setting:

    When we select the

      Restrict view access to this page to community members

    ...setting, the following changes are made:

    • The User role on the page is assigned to the virtual user group that represents the members of the associated community.

    • Role blocks are added on the page for the User role and the Privileged User role.

    When you clear the...

      Restrict view access to this page to community members

    ...setting, the following changes are made:

    • The User role on the page is removed for the virtual user group that represents the members of the associated community.

    • The role blocks on the page for the User role and Privileged User role are removed.

    If you change the community associated with the page, the following changes are made:

    • The User role on the page is removed for the virtual user group that represents the members of the previously associated community.

    • The User role on the page is assigned to the virtual user group that represents the members of the newly associated community.

    • If role blocks do not exist on the page for the User role and Privileged User role, the role blocks are created.

    Activating this feature is restricted to users that are granted all roles required if the corresponding access control modifications are performed manually with the access control administration portlets.

  4. If you want child pages of this page to be automatically associated with the same community as this page, click the setting to copy the updated association to child pages.

    This setting associates the community to all child pages where the user has sufficient access to update page associations. If the user does not have the required access for a page, it is not updated.

    Depending on the configuration of the server, the window displays the number of pages and nesting levels that are affected based on a threshold. If the number of affected pages exceeds the configured threshold value, this option is not displayed.

    When community associations for a page are copied to child pages, only the community associations are copied. The value of the...

      Restrict view access to this page to community members

    ...setting is not copied to child pages because of access control inheritance. This inheritance automatically enables members of the mapped community to view the child pages.


Create a community association using xmlaccess.sh

When defining the association in the XML import file, use the element...

...and specify a content mapping scope of...

...for an individual nested element...

This XML sample shows how to map a page to a community. In this example, the page has the unique name...

...and the community is specified with the community UUID...

...in IBM Connections. 

<request type="update" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"           
         xsi:noNamespaceSchemaLocation="PortalConfig_8.0.0.xsd">

    <portal action="locate">
        <content-node action="update"  
                      domain="rel" 
                      uniquename="unique-name-of-the-page-to-be-updated">

            <content-mapping-info>
                <content-mapping content-id="some-ibm-connections-community-uuid" 
                                 default="true" 
                                 scope="ibm.connections"/>
            </content-mapping-info>

        </content-node>
    </portal>
</request>


Parent: Manage community pages
Related:
Access permissions
Automatically grant page access to community members
xmlaccess.sh and content associations