the parent organizations containing BostonWebHost_Windows. For example, users assigned to BostonWebHosts would also see the addition because it contains BostonWebHost_Windows; users assigned to only BostonWebHost_Solaris would not see the addition.
A child organization can be in multiple parent organizations. As shown in the following figure BostonWebHosts and NYWebHosts are not only children of the WebHosts organization, but they are also children of the US East Coast organization. For example, if you have a user that oversees all Web hosts in the company, you could assign that user to the WebHosts organization. Users managing hosts and storage systems on the East Coast would be assigned to the US East Coast organization, which is a parent of BostonWebHosts, NYWebHosts, and StorageSystems organizations. For example, if an element is added to NYWebHost_Solaris, users assigned to one or more of the following organizations would see the addition:
•NYWebHost_Solaris
•NYWebHosts
•WebHosts
•US East Coast
Figure 23 Children in Multiple Organizations
When you remove an element from an organization, users belonging to that organization or to one of its parents can no longer access that element if it is not a member of any other organization. For example, assume an element named MyHost was not only a member of BostonWebHost_Solaris, but also had mistakenly became a member of BostonWebHost_Windows. If you remove MyHost from BostonWebHost_Solaris, users belonging to BostonWebHost_Solaris can no longer access the element. Users belonging to the following organizations would still see the element because the element is still a member of BostonWebHost_Windows.
•BostonWebHosts
•WebHosts
•US East Coast
354 Managing Security