We would like SolarWinds to provide more granular administrative permissions across configuration objects. Currently, administrative rights are generally assigned at a feature level, meaning that granting a user or team access to manage a particular component often provides visibility and modification rights to all instances of that component across the platform.
For example, we need the ability to create administrative groups that can manage only their own configuration objects, such as:
- Alerts
- API Polling configurations
- Dashboards
- Reports
- SAM Templates
- Nodes and monitoring assignments
While Account Limitations help restrict access to monitored objects and underlying datasets, they do not provide true ownership-based administration of SolarWinds configurations. As a result, when delegated administrators are granted read/write permissions, they can typically view and modify configurations belonging to other teams.
In a large enterprise deployment with multiple operational teams sharing the same SolarWinds environment, this creates governance, security, and change-control challenges. Teams require the ability to independently administer their own monitoring content without having visibility of, or the ability to modify, configurations owned by other teams.
The desired functionality would allow organizations to:
- Assign ownership of configuration objects to specific teams or groups.
- Delegate administration on a per-object-type basis.
- Restrict visibility so teams only see configurations they own.
- Allow configuration management without requiring full platform administrative permissions.
- Maintain separation of duties while still supporting self-service administration.
Example:
Team A should be able to create, edit, and delete only their dashboards, alerts, reports, and SAM templates.
Team B should have the same capabilities for their own assets.
Neither team should be able to view or modify the other team's configurations, while central SolarWinds administrators retain full global control.