Roles and access
Create company roles with permissions by module and the inventory scope they see; Core, Incidents and Dashboards are required in every role.
On this page
The built-in roles (Administrator, Operator and Viewer) don't change. If you need something in between, create a company role: you choose the permission level in each module and which part of the inventory it sees.
Permission levels
Level | What it allows |
|---|---|
No access | The module doesn't appear in the menu |
View | Look up information |
Operate | Also acknowledge, snooze, test and run checks |
Administer | Also create, change, delete and configure |
Required modules
Every role sees at least the following, and they can't be set to No access:
Dashboards.
Incidents and events.
Core (groups, sites, alarm policies, resolver groups and notification rules).
In the matrix they appear with the required label.
Modules in the matrix
Modules are grouped as in the menu: Monitoring (Dashboards, Operations map and NOC screen), Infrastructure (Servers and hosts, Databases, Cloud services, Agents, Plugins, Network), Applications (Web and TCP services, UX tests, APM), Operations (Incidents and events, Cerebro, Core, Assistant), Security (SIEM security, Vulnerabilities) and Administration (Settings).
Inventory scope
A role can see The whole inventory or Only part of it: some groups (with their subgroups), entire types (for example, all databases) or specific items. With a partial scope, in Security and Vulnerabilities the role sees only what belongs to the servers in its scope.
In the role list
You see the built-in roles and the company roles, with their permissions, their scope and who has them. Each company role has View as, Edit and the trash can icon.