Figure 7 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
Keep in mind the following:
•You cannot edit the Everything organization.
•If you don't want users to have access to all elements, remove them from the Everything organization.
•Users can access information about all elements from security pages. For example, if a user is assigned to an organization that has access to only hosts, the user can still see information relating to storage systems on the security pages. accessible from the SE Home page
•Because generic elements cannot be placed into organizations, they do not appear unless the user belongs to the Everything organization. You can tell if an element is generic by
•Discovery lists in HP SE (Discovery tab on the SE Home page) are not filtered. Users can see all elements in the discovery lists regardless of their affiliation with an organization.
•Event Manager displays events from all elements regardless of the user’s organization.
130 Managing Security