What We're Working On for The Orion Platform (Updated: July 15, 2021)

CURRENT RELEASE 

The latest release of  the Orion Platform 2020.2.6 is available on solarwinds.com and in your customer portal. We hope you're enjoying the features of our current Orion Platform 2020.2.6

What We're Working On

  • Support SHA256/512 for SNMPv3 
  • GMSA Account for the Orion database.
  • Simplified installation via single MSI
  • Additional credential management via API.
  • jQuery update
  • Validation of CIS IIS and SQL Server best practices
  • Removal of any code unsupported by Microsoft

GIVE US FEEDBACK 

You ask, we listen. Many of the top features developed are generated through your participation in user sessions and your votes in the feature requests forum.  

Anonymous
Parents
  • One thing we really would like to see is better permissions granularity.

    Essentially what we'd like to see is:

    • Super Admin level - can do anything
    • Admin - can only edit certain, specific areas e.g. reports
    • Power User - can access all areas, can add certain aspects (e.g. reports) but can't edit other areas e.g. node properties
    • User - can access all areas but has no write/change capability
    • Some other level - IOW can be a combo of any or none of the above

    Also, modern dashboards needs to be brought under control of user permissions so that it can be locked down as needed.

    We have a lot of tech savvy users that like to fiddle and think they know a product just from a few minutes play. But to create a report (hardly life changing or system destroying) we need to provide admin level access - which is NUTS.

  • Totally agree with this, I think I've sumbitted an idea YEARS ago for permission granularity for the reason you mention but also for the possibility to have different read and write accesses for the same account.

    i.e. Sees everything but can edit nodes of a particular area (custom property based).

    Now you can set view limitation based on custom properties.. but that's not very granular, one should be able to view everything but edit some aspects locally.

Comment
  • Totally agree with this, I think I've sumbitted an idea YEARS ago for permission granularity for the reason you mention but also for the possibility to have different read and write accesses for the same account.

    i.e. Sees everything but can edit nodes of a particular area (custom property based).

    Now you can set view limitation based on custom properties.. but that's not very granular, one should be able to view everything but edit some aspects locally.

Children
No Data
Thwack - Symbolize TM, R, and C