Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Account limitations

How can you limit accounts to only view some nodes, but have full access to others?

For example, The virtualization detail web part errors when viewing a node with account limitations for that node, because the account cannot access the vCenter or ESXi host.

Find more posts tagged with

Accepted answers

All comments

pratikmehta003

You can create account limitation for a View by selecting the nodes required. Give admin rights overall in each plugin.

dfairles

This has to do with the fact also that virtual nodes are separate from regular nodes if you have VIM

pratikmehta003

so u have few accounts who should be restricted to view X nodes( not virtual nodes) but should still be able to access the virtual nodes, correct?

i_like_eggs

hey,

you can group views by Custom properties and build your limitation on the custom property. you will need to log on to the primary soalrwinds server and open 'account limitation builder'

then on your view select edit

and select the CP

you will have to play around with the accounts and nodes details views

id probably go with this option: why not just select the accounts that dont need to have the access to the Virtual environment and remove the view completely

dfairles

The custom property will not be on the virtualization node. When you have VIM, it creates a separate nodes table just for the virtualization nodes, and that table is linked to the nodes table. That is the issue. They need to see the virtualization details that the custom property knows nothing about.

You have to build 2 sets of account limitations. One for the node, and another for the virtual node. Since you can't add a custom property to the virtual node, you are stuck with name pattern.