Converting a dynamic group to a basic group
When converting a dynamic group to a basic group, the membership rules only are removed from the group. The group membership list remains unchanged. To convert a dynamic group to a basic group, right-click the group, and then click Convert to Basic Group. In the confirmation message box, click Yes.
When a group is no longer dynamic, it becomes a basic group with the following characteristics:
- The Membership Rules tab disappears from the Properties dialog box.
- The Members tab allows you to add and remove members (the Add and Remove buttons appear on the Members tab).
Modifying, renaming, or deleting a dynamic group
You can manage dynamic groups in the same way as you manage basic (regular) groups — rename, modify properties, assign a Trustee when delegating control, and delete. The instructions on how to perform such management tasks on a Dynamic Group are the same as for regular groups. For step-by-step instructions on how to manage groups, see the “Group Management Tasks” section in the Active Roles User Guide or Active Roles Help.
Scenario: Automatically moving users between groups
This scenario removes a user from the Seattle group and adds the user to the Atlanta group when the user relocates to Atlanta from Seattle.
Suppose user accounts of employees working in Seattle belong to the Seattle group, and user accounts of those working in Atlanta belong to the Atlanta group. The group to which the user belongs is defined by the city attribute: employees working in Seattle have user accounts with the value Seattle for the City attribute. For those working in Atlanta, the value is Atlanta.
To implement this scenario, you must perform the following actions:
- Create the Seattle and Atlanta groups.
- Configure membership rules to add users with a city value of Seattle to the Seattle group, and those with Atlanta to the Atlanta group.
As a result, only user accounts that currently have a city value of Seattle belong to the Seattle group. Thus, when an employee leaves Seattle for Atlanta, an administrator changes the City attribute from Seattle to Atlanta, and the user automatically moves to the Atlanta group because of the membership rule. Conversely, when an employee leaves Atlanta for Seattle, the administrator changes the city attribute from Atlanta to Seattle, and the user automatically transfers to the Seattle group.
The following sections elaborate on the steps to implement this scenario.
Step 1: Creating the groups
To create the Seattle group, in the console tree, right-click the container where you want to add the group, and select New | Group. Follow the instructions in the New Object – Group wizard. In the Group name box, type Seattle.
To create the Atlanta group, in the console tree, right-click the container where you want to add the group, and select New | Group. Follow the instructions in the New Object – Group wizard. In the Group name box, type Atlanta.