A Super Admin can manage alerts only within the organizations, sites, and account contexts to which the Super Admin has access. If an Alerts v2 alert cannot be edited, the issue may be related to the current dashboard context, alert scope, or user permissions.
Why this happens
Common causes include:
- You are viewing a different organization, multi-site, or site than the one associated with the alert.
- The alert is managed at a parent or organization level, but you are viewing it from a child-site context.
- Your role has Manage Alerts: View instead of Manage Alerts: Edit.
- The alert applies to sites or organizations that are outside your current access scope.
- The alert is inherited from a parent level and must be changed at that level.
- The alert is a Legacy alert being viewed from the Alerts v2 area, or an Alerts v2 alert being viewed from the Legacy alert area.
- Your session does not reflect a recent role or access change.
Super Admin access does not override the account or site context in which the alert is being managed. A Super Admin must still work from an authorized organization or site context.
Confirm the alert type
Before attempting to edit the alert, confirm whether it is a Legacy alert or an Alerts v2 alert.
- Go to Manage Alerts.
- Open the appropriate alert table or alerting experience.
- Locate the alert.
- Check the alert source or alert type, where available.
- Confirm that you are attempting to edit it from the correct alerting experience.
Legacy and Alerts v2 alerts may monitor similar conditions but are separate alert definitions. Editing one does not modify the other.
Confirm the current account context
Check the account hierarchy shown in the Auvik interface.
Confirm that you are working from the:
- Correct MSP or root organization
- Correct multi-site
- Correct child site
- Correct tenant or client account
If the alert was configured at a parent or organization level, open Manage Alerts from that level and locate the alert there.
If the alert is intended to apply only to one child site, open the child site and check whether a site-specific alert definition exists.
Check the alert’s scope
Review the alert’s configured scope to determine which sites, devices, interfaces, collectors, or other entities it applies to.
An alert may appear unavailable for editing when:
- Its scope is outside the current site.
- The alert is inherited from a parent level.
- The current user does not have access to all sites included in the alert.
- The alert definition is being viewed from a filtered or child-site context.
If the alert applies to multiple sites, make changes from the level where the alert is managed and where you have access to the required sites.
Check user permissions
To view alert definitions, the user needs:
- Manage Alerts: View
To create, edit, enable, disable, or delete alert definitions, the user needs:
- Manage Alerts: Edit
If the alert uses tags and the user needs to create, edit, or delete those tags, the user may also need:
- Manage Tags: Edit
View-only access is not sufficient to modify an alert definition.
Ask a Super Admin or role administrator to verify the assigned role and site or organization access if the required permissions are missing.
Refresh the session
If your role or site access was recently changed:
- Save any work in progress.
- Sign out of Auvik.
- Sign back in.
- Select the correct organization, multi-site, or child-site context.
- Return to Manage Alerts and try again.
Refreshing the session may help if the interface is still using an earlier permission state. It will not grant access that the user’s role does not include.
If the alert is inherited
If the alert is inherited from a parent or organization level:
- Open Manage Alerts from the parent or organization context.
- Locate the alert definition.
- Edit the alert at that level if you have Manage Alerts: Edit access.
- Save the change.
- Confirm how the change affects child sites.
Make parent-level changes only when the change is intended to affect all sites using that inherited configuration.
If a child site requires different behavior, use a supported child-site override or clone the alert at the appropriate level. Review the resulting scope and notification channels before saving.
If you cannot edit the alert at its current level
If you do not have access to the level where the alert is managed:
- Ask an administrator with access to that organization or site to make the change.
- Ask the administrator to update your role or site access if you should manage the alert yourself.
- Provide the alert name, affected site or sites, required change, and the error message shown in Auvik.
Do not create a replacement alert until you confirm whether the original alert is still active. Creating a second alert for the same condition may result in duplicate notifications.
Creating a replacement or cloned alert
If you are authorized to create alerts at your current level and a separate alert is appropriate:
- Confirm the original alert’s scope and notification channels.
- Clone the alert or create a new Alerts v2 alert.
- Configure the required scope, conditions, severity, clear condition, and notification channels.
- Save the new alert.
- Confirm that the new alert is enabled.
- Disable or remove the original alert only if it is no longer required.
- Test the resulting notification behavior.
Disabling or deleting the original alert requires Manage Alerts: Edit access.
If the problem continues
Collect the following information before contacting an Auvik administrator or Auvik Support:
- Alert name
- Alert source, if shown
- Current MSP, organization, multi-site, or site context
- Site or sites included in the alert
- Your assigned role
- The permission level shown for Manage Alerts
- The exact error message
- Whether the alert is inherited, cloned, or site-specific
- The approximate time the issue occurred