Applications Systems
Non-admin users cannot access the “Manage Maintenance Schedules” page or create recurring maintenance schedules in the SolarWinds Platform
Non-admin users cannot currently access the Manage Maintenance Schedules page; this functionality is restricted to accounts with the Administrator role. Even with permissions like Node Management or Allow Account to Unmanage Objects & Mute Alerts, users can only schedule one-time maintenance and assign/cancel existing schedules via Maintenance Mode,
First published date
Last published date
Overview
Overview
In current SolarWinds Platform versions, access to the Manage Maintenance Schedules page is limited to users with the Administrator role.
Non-admin users can participate in maintenance operations only through permissions such as Node Management and Allow Account to Unmanage Objects & Mute Alerts, which let them schedule one-time maintenance and assign or cancel existing schedules via Maintenance Mode on nodes, groups, or other entities. However, these rights do not provide access to the central Manage Maintenance Schedules interface or the ability to create and manage recurring schedules.
This behavior is by design and is recognized as a product limitation; a Feature Request has been raised to introduce granular, role-based permissions so organizations can delegate maintenance schedule management to operations or NOC teams without granting full Administrator access.
Product section
Cause
As of the above versions, the Manage Maintenance Schedules (Schedule Management) page is restricted to accounts with the Administrator role. There is no separate granular permission that exposes this page to non-admin users.
While non-admin accounts can have rights like Node Management or Allow Account to Unmanage Objects & Mute Alerts, these permissions only allow them to:
- Schedule one-time maintenance from entity grids and details pages
- Assign or unassign existing schedules to entities they are allowed to manage
They do not grant access to the central Manage Maintenance Schedules UI.
Resolution
- Currently, there is no supported way to grant access to the “Manage Maintenance Schedules” page without giving the user full Administrator rights.
- To allow users to work with maintenance without full admin:
- Assign the user Node Management and/or Allow Account to Unmanage Objects & Mute Alerts, depending on your security requirements.
- Have those users:
- Schedule one-time maintenance from the Maintenance Mode options on Manage Nodes, Manage Groups, or from object details pages.
- Assign or cancel existing recurring maintenance schedules that administrators have already created.
-
If you need operations/NOC users to fully create and manage recurring maintenance schedules, this is currently a product limitation and must be handled by administrators.
Workaround
- Use a process where:
- Administrators:
- Create and maintain the recurring maintenance schedules in Manage Maintenance Schedules.
- Non-admin operators:
- Use the Maintenance Mode actions (one-time maintenance, assign/cancel existing schedules) for day-to-day operations.
- Administrators:
- Optionally, maintain an internal request workflow (e.g., ticket or change request) so non-admin teams can request new or updated recurring schedules from admins.
Status / Feature Request
- This limitation is tracked as an existing Feature Request to introduce granular, role-based permissions for Manage Maintenance Schedules, allowing non-admin users to access and manage schedules without full Administrator rights. You may also Submit a Feature Request to help prioritize the improvement of this limitation.
- As of April 29, 2026, there is no released version in which this granular permission is available.
- This limitation is tracked as an existing Feature Request to introduce granular, role-based permissions for Manage Maintenance Schedules, allowing non-admin users to access and manage schedules without full Administrator rights. You may also Submit a Feature Request to help prioritize the improvement of this limitation.
- Use a process where: