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

Account Limitations in Modern Dashboards

Hi folks,

Version 2024.3, update to 2025.2 pending.

Our users are split into two teams with each team being able to see just their own nodes based on a custom property account limitation. This works well in all respects and appears to be applied on modern dashboards APART FROM the Security → Vulnerability and Risk Dashboard where each team will see the full details of their own nodes, but the other team's nodes will appear as a series of dashes instead of data.

If a user clicks on a CVE ID that only affects the OTHER team's nodes they get an error in the browser, click on the error and you get this:

This says to me that the account limitation isn't being applied just on this dashboard.

I'm guessing the answer will be 'upgrade to 2025.2' which is planned. We can't go any higher because 2025.4 and above breaks cloud account monitoring and there's no fix yet. Our test environment is 2025.2 so I'll run some tests tomorrow, but in the meanwhile if anyone else has come across this I'm all ears.

Cheers
Adrian

Find more posts tagged with

Accepted answers

All comments

cnorborg

Yea, I think its documented somewhere that account limitations don't apply to Modern dashboards. I thought they had added it in 2024.4, but instead it was something called Global Filters.

https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-fusion-edit-filter.htm

Doesn't work like I would want it to!

The only "fix" is to build the limitations into the actual SWQL query that you do.

fop

This was the conclusion I ended up at yesterday, so I set about trying to work out how I could grab the account limitation of the logged in user and apply that to the custom property in the SWQL or use on a global filter.

It seems like I can't get info of the logged in user because that just isn't stored anywhere, but obviously the rendering engine knows it so I'm surprised it's not stored in a system variable. Maybe it is and I've just not found it yet.

fop

OK, I set up an identical account limitation in my homelab and it looks like it does actually work properly in 2025.2 - one team sees 'their' nodes and the other team sees their own in the Vulnerability Dashboard.

I guess that's the final push I need to make me get that upgrade scheduled!

Cheers

fop

The plot thickens. For a SYSTEM Modern Dashboard like the Vulnerability and Risk it works as expected, but the second you unlink the SWQL queries to create a modified version of that dashboard the account limitations are ignored.

So I'm back to square one trying to get the limitation of the logged in user so I can apply it to the query. There MUST be a global filter for this.

(Reason we're creating a modified version of that dashboard is a) to make it multi-customer and show the customer name against each node and b) to show critical CVEs, ie a score over 9)

cnorborg

Yea, the only way I've figured out how to do it is copy the dashboard for each group and create their own copy baking in their own limitations into the SWQL. Kind of a pain, but…

fop

Success! Kind of. Using the SQL Profiler I tracked down the actual query the poller was using to capture the node data and sent it to a colleague who's SQL is far better than mine. He said that a LEFT JOIN I'd used would work better as an INNER JOIN so I changed the query and lo, the blank lines and dashes went away and I get the correct limited data.

I need to check next week because I don't think ALL the queries on that dashboard return the limited data in which case I will do separate dashboards per team, but that was a small victory which was bugging me