You can move a top-level community to become a subcommunity of another community, or you
can move a subcommunity to become a top-level community. You can also move a subcommunity from one
parent community to another.
Before you begin
You must be a community owner
both in the community that is being moved and in the intended parent community.
Note: You can only
move a community or subcommunity to a new parent of the same type (that is, an internal or external
community). For example, you can only move an external restricted community or subcommunity to a new
parent community that is also external restricted. Similarly, you can only move an internal
community or subcommunity to a new parent that is also internal.
Also, if you move a restricted
but listed community under a community that is restricted but not listed, the moved community will
no longer be listed. For more information, see Creating communities.
About this task
Moving stand-alone communities to be subcommunities of a top-level, parent community is a
good way to integrate what were diverse communities. Similarly, moving a subcommunity to make it a
top-level community is a good way to promote important communities.
Procedure
Take one of the following steps, depending on whether you want to
- Make a top-level community into a subcommunity of another community.
- Move a subcommunity from one parent community to another.
- Make a subcommunity into a top-level community.
.
Note: Moving a community might involve changes (such as adding members to the parent, adding
owners to the subcommunity, or changing the access level of a community) that cannot be
undone.
- To make a top-level community into a subcommunity, complete the following steps.
- Log in to IBM® Connections and open the community that you
want to move.
- On the Members page, select the Invitations tab
and record any invited users.
Note: When you move a community, any users that are invited to join the community are removed. You
can reinvite these users when the move is complete.
- From the Overview page, select .
- Select Make this a subcommunity of: and begin typing the name of the
intended parent community. Select a community from the type-ahead list returned and click
Move. A list of people to be added as members to the parent community or as
owners to the subcommunity might be displayed. If the membership list is long, select
Show more members to be added to scroll through the entire list.
- If required, confirm that you want to add the members or owners, and click
Move again, the top-level community is now a subcommunity of the community
you specified, this relationship is known as a parent-child relationship.
The new subcommunity is modified as follows:- Any users that are invited to join the subcommunity and did not accept or decline the
invitation are removed. Click the Invitations tab. You can see that the
invited users no longer appear on the Invitations tab.
When you move a community, the following changes might be made depending on the membership
and access level of both communities:
- The access level of the community that is being moved might be modified to be at least as
restrictive as its new parent.
- Members and owners in the community that is being moved are added to the new parent, if they are
not there already.
- Owners in the new parent are added to the subcommunity that is being moved.
- To move a subcommunity from one parent community to another, complete the following
steps.
- Log in to IBM Connections and open the subcommunity that
you want to move.
- On the Members page, select the Invitations tab
and record any invited users.
Note: When you move a subcommunity, any users that are invited to join the subcommunity are removed.
You can reinvite these users when the move is complete.
- From the Overview page, select .
- Select Make this a subcommunity of: and begin typing the name of the
intended parent community. Select a community from the type-ahead list returned and click
Move. A list of people to be added as members to the parent community or as
owners to the subcommunity might be displayed. If the membership list is long, select
Show more members to be added to scroll through the entire list.
- If required, confirm that you want to add the members or owners, and click
Move again, the moved subcommunity is now a child subcommunity of the
top-level community you specified.
The new subcommunity is modified as follows:- Any users that are invited to join the subcommunity and did not accept or decline the
invitation are removed. Click the Invitations tab. You can see that the
invited users no longer appear on the Invitations tab.
When you move a subcommunity, the following changes might be made depending on the
membership and access level of both the subcommunity and the new parent community:
- The access level of the subcommunity that is being moved might be modified to be at least as
restrictive as its new parent.
- The following membership changes might be made:
- To make a subcommunity into a top-level community, complete the following steps.
- Log in to IBM Connections and open the subcommunity that
you want to move.
- On the Members page, select the Invitations tab
and record any invited users.
Note: When you move a subcommunity, any users that are invited to join the community are removed and
would need to be reinvited.
- From the Overview page, select .
- Select Make this a top level community.
- Click Move, the subcommunity is now a top-level community.
- Optional: You can now reinvite any users that were removed from the community
invitation list. For more information, see Inviting people to join a community.
Results
A subcommunity cannot be less restrictive than its parent. Therefore, when you move a
community, the access level of the community that is being moved to a subcommunity can be modified
as shown in table 1.
Note: Table 1 shows the changes that might occur when you move a top-level
community to become a subcommunity of another top-level community. Similar changes can occur, if you
move a subcommunity, to have a new parent community.