We have several groups that make use of solarwinds based on AD group.
We would like to give them the ability to add, remove, edit their own nodes but not to affect the other groups. Anyway to restrict management access of nodes by Group?
You will need to give the group Node Management rights and then apply limitations appropriate for the nodes that they are managing. The tricky part is that the limitations will need to be of a dynamic nature such as the Node Name Pattern. If you use a single node or group of nodes, when the users add a new node, the will not be able to see it. By using a Name Pattern, as long as the nodes are named appropriately, they will be able to manage only those nodes defined by the Name Pattern.
Thank you for your response. I appreciate the time and effort for you to take to answer my question. Looking at my question, I should have stated it clearer.
We would like them to manage their nodes, we use a Custom Field called Support_Team. But also be able to have view nodes that they have a parent daughter relationship.
A good example. Group A manages the servers they are responsible for. But they need view only of the network switches the servers are connected to and IPSLA functions functions related to those switches. But they cannot have edit or manage rights. Just view only.
I tried using the Hardware Health overview and Application Health Overview with the Support_Team Account limitation and not only do both Overviews fail but I only get their servers
I hope that is a bit clearer.
I wondered if that was where you were going with this as I thought that my answer might be a little limiting. I have similar needs for a more granular security model, but I have yet to find a way to allow a user to manage certain nodes and not others using the same user account. Likewise, I don't beleive there are any permissions built around the use of Custom Fields.
