Permission Set for Monitor Views
The Monitor View permission set decides which Monitor Views the members of a Role can open, and what they may do with the monitored Resources inside: run Remote Actions, view metrics and alert history, and read the related Repository Model information and Knowledge Base Articles. With it, operations and business teams can fix their own problems without full administrator access.
- ✅ Granular access control for Monitor Views
- ✅ Role-based security for users and teams
- ✅ Separate rights for Remote Actions, metrics, history, repository, and articles
- ✅ Global defaults with per-Monitor View overrides
This page is for administrators. How end-users work with a Monitor View is covered in Getting Started with Monitor.
Understanding the Monitor View Permission Set
The Access permission is the gate: without it, a Role sees no Monitor Views at all. Each other right has a global value and a value per Monitor View; Inherited on a Monitor View takes the global value.
Access + defaults"] -->|"Allow or Deny"| A["fa:fa-search Access
per Monitor View"] G -.->|"Inherit, Allow, or Deny"| X["fa:fa-bolt Execute Actions"] G -.->|"Inherit, Allow, or Deny"| ME["fa:fa-chart-line View Metrics"] G -.->|"Inherit, Allow, or Deny"| H["fa:fa-history View History"] G -.->|"Inherit, Allow, or Deny"| R["fa:fa-sitemap View Repository"] G -.->|"Inherit, Allow, or Deny"| AR["fa:fa-newspaper View Articles"] style G fill:#2678BD,color:#fff style A fill:#E47528,color:#fff style X fill:#9E59BB,color:#fff style ME fill:#3F827B,color:#fff style H fill:#3F827B,color:#fff style R fill:#3F827B,color:#fff style AR fill:#3F827B,color:#fff
Blue = global permissions, orange = access to the Monitor View, purple = the right that changes monitored systems (Remote Actions), teal = read rights.
| Permission | What it unlocks | Also depends on |
|---|---|---|
| Access | The Monitor View is listed and its Resources shown | Global Access set to Allow |
| Execute Actions | Control Center Remote Actions in the Action menu | The Resource type (actions vary per agent) |
| View Metrics | The Metrics section of the Action menu | The Resource type |
| View History | Alert history for the Resources | DaysToKeepMonitorEvents limits how far back |
| View Repository | The Repository Model tab with related Integrations | Repository Model bindings for the Resource |
| View Articles | Knowledge Base Articles on Resources | Articles linked to the Resource |
Global Permissions
The global Access permission, on the Monitor Views row under Global permissions, controls whether a user can use the Monitor functionality at all. It must be set to Allow for users to see any Monitor Views. The Permissions row sets the global value of every other right.
The Monitor Permissions (13) tab of the Finance Role: global Access and default rights on top, the assigned Monitor Views below with a filter box, Include deleted, and Edit to add or remove views.
Access Monitor
To use Nodinite Monitor Views, a User must be a member of a Role granted Allow in the Access column of the Monitor Views row under Global permissions.
Note
If the User is a member of any Role where access to the Monitor is denied (Deny), the user is blocked from ALL Monitor Views.
1: the global Access right on the Monitor Views row. 2: the Access right on one Monitor View, picked from the Set permit list.
- The Role is set to Allow access to the Monitor Views under Global permissions.
- The Role can have different Access rights to individual Monitor Views.
- ✅ Allow - the Monitor View is visible and accessible to the end-user.
- ❌ Deny - the Monitor View is NOT visible or accessible to the end-user.
You can also add a Role from the Monitor View itself, in Add or manage Monitor View. The DefaultRolesInViews System Parameter pre-selects Roles on every new Monitor View.
Monitor View Permissions
The following permissions can be set individually for each Monitor View:
Execute Actions
Members of Roles with Execute Actions may perform Remote Actions on the Resources in the Monitor View. The actions in the Control Center section of the Action button depend on the type of Resource.
Remote Actions for a queue Resource, such as Resubmit, Purge, Enable, and Disable.
- Inherited - Remote Actions in the Control Center section are available IF the global setting is Allow; otherwise, they are not.
- Allow - Remote Actions in the Control Center section are visible and operational.
- Deny - Remote Actions in the Control Center section are NOT visible or operational.
Tip
For the available Remote Actions, use cases, and how end-users run them, see Remote Actions. Every Remote Action is recorded in Log Audits.
View Metrics
Members of Roles with View Metrics may view metrics and statistics for the Resources in the Monitor View. The metrics in the Metrics section of the Action button depend on the type of Resource.
The Metrics items differ per Resource type.
- Inherited - Items in the Metrics section are available IF the global setting is Allow; otherwise, they are not.
- Allow - Items in the Metrics section are visible and operational.
- Deny - Items in the Metrics section are NOT visible or operational.
A Nodinite Administrator can also show Metrics on the Dashboard and in configured Monitor Views.
View History
Members of Roles with View History may view the alert history of the Resources in the Monitor View. The history is available from several places in the Web Client.
- Inherited - Alert history is available IF the global setting is Allow; otherwise, it is not.
- Allow - Alert history is visible.
- Deny - Alert history is NOT visible.
The history is limited in time by the DaysToKeepMonitorEvents System Parameter.
| Search | Resource history |
|---|---|
 Search for alert history for all resources in the Monitor View |
 Alert history for the selected Azure Storage item (in this case, a Blob Container) |
The View History tab lists state changes for the Resources in the Monitor View.
View Repository
Members of Roles with View Repository may view information about the Integrations related to a Resource, as defined in the Repository Model. What they may do in the Repository itself is set by the Permission Set for the Repository Model.
- Inherited - Related Integrations are available in the Repository Model tab IF the global setting is Allow; otherwise, they are not.
- Allow - Related Integrations are available in the Repository Model tab.
- Deny - Information about the Integrations is NOT available.
The Repository Model tab connects a Resource to the Integrations it is part of.
View Articles
Members of Roles with View Articles may read the Knowledge Base Articles linked to the Resources in the Monitor View.
- Inherited - Related Articles are available IF the global setting is Allow; otherwise, they are not.
- Allow - Related Articles are available in the Monitor View.
- Deny - Articles are NOT available in the Monitor View.
The article icon shows how many Articles are linked to the Resource; click it to read them.
Permission Inheritance and Summary
The net rights of a User are the combination of all their Roles. If any Role has Deny on the Monitor, the user is denied all Monitor Views regardless of other permissions. Open a User in Add or manage User to see the result.
The User editor shows the net (effective) Monitor permissions for that user, across all of their Roles.
Next Steps
Add or manage Role
Add or manage Monitor View
Permission Set for the Repository Model
Related Topics
Log View permission set
Repository Model permission set
C4 Diagram Set permission set
What is a Role?
Access Management
Monitor Views
Monitor Views Overview
Getting Started with Monitor
Remote Actions
Users
DefaultRolesInViews – Roles pre-selected for new Monitor Views