cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post

Granular Node Management Rights.

Granular Node Management Rights.

There needs to be a simple way to assign users specific node management rights. For example, i have a group of users that i only want to be able to unmanage nodes, nothing more. There may be sophisticated ways of achieving this but it would be nice to have it built into the "Manage Accounts" section.

Thanks for considering this.

137 Comments
Level 9

This very issue is causing me pain today.

We allow our NOC users to unmanage devices.  Because they don't have access to the "Manage Nodes" page, the only way for them to unmanage a group of devices is one at a time on each node's page. 

It's insane that Manage Nodes isn't widely available with only the buttons that users have access to enabled.

Level 11

This is a big need. Hopefully it gets addressed.

Users need access to the Manage Nodes screen having full node management privs.

Maybe just separate deleting nodes/interfaces from node management?

Any news on this?  Maybe someone has a workaround.

Level 10

Bump from me too...

Bump!

I'm mostly looking for the ability to limit accounts to unmanage/mute nodes for 90 days.  It was an easier policy to enforce before the most recent upgrade sets the date to as close to the year 10,000 as possible with the simple click of a button.

Level 9

Solarwinds, please work on this request. Very important for us.

For us it would be great if group permissons are additive and permissions does not only come from the highest prio group.

Level 9

Always same question from user without answer.

For large customer we currently have difficulties to adapt the software for a central console in terms of rights management

Team need to have “only view on specific part / device” and “administration on another scope”, it could be done with 2 unique users login with 2 groups… but frequently end user has only one account and we can’t ask to the customer to create another account to restrict view… and this workaround is not acceptable because team spend a lot of time to know what is the login for this action and what is the login for the other action.