Face your biggest database issues head-on
Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.
Register for your free eCourse.
Updated August 3, 2016
This article provides steps to create groups in IPAM and set account restrictions to limit visibility.
All IPAM versions
1. Go to the Manage Subnets and IP address Tab.
2. Add a new group and rename it, for example, Parent.
3. Select this group and then add another group as a sub group.
4. Repeat this step to generate more sub groups.
5. Once you have added all your subgroups, you can now edit the group to apply permissions.
Note: You do not need to edit the Parent group as its permission is hidden by default, and needs to remain as hidden. The parent group needs to have the highest restrictions. If you are hiding a sub group, the parent also needs to have the Hide permission applied.
6. Go to Sub Group 1 and edit it.
7. Select +, next to Account roles , and then Expand it.
8. Select an account you would like to have access to the sub group.
a. Select Change role.
b. Add the permission required from Power User / Operator/ Read Only.
c. Select Save.
If you now log on to the Account with the restriction in place you will see the Group tree but will only be able to see the contents of a group were you have a permission of read only as a minimum.
