User Role Definitions

When you invite a user account to access Riverbed IQ Ops, you must assign a role to that account according to the access/capabilities needed by that user. For more information about how Role-Based Access Control (RBAC An observed change in a specific metric stream that is recognized as being outside of an expected model. Indicators are correlated into triggers, and one or more triggers are grouped into incidents.) works throughout the system, see Role-Based Access Control.

Refer to the table below for access/capabilities associated with each Role:

UI Area	Read	Write	Admin	Notes
Impact Dashboard	✓	✓	✓
Incidents A collection of one or more related triggers. Relationships that cause triggers to be combined into incidents include application, location, operating system, or a trigger by itself.	View-only	✓	✓	View-only cannot save changes to the associated Runbook An automated workflow that executes a series of steps or tasks in response to a triggered event, such as the detection of anomalous behavior generating an incident, a lifecycle event, or a manually executed runbook..
Runbook Analyses	View-only	✓	✓	View-only cannot save changes to the associated Runbook.
Runbook Scheduling	✓	✓	✓
Automation Automated procedures that are executed as the result of a trigger. Automations consist of a single entry point and a sequence of connected nodes that define the processing logic.	View-only	✓	✓	View-only cannot save changes to associated Runbook.
Explorer	✓	✓	✓
Integrations Library	View-only	View-only	✓	View-only can view Installed and Available Integrations A runbook node category that works with other applications, such as HTTP calls, to enable communication with external systems and third-party tools..
Administration	❌	❌	✓
Support	✓	✓	✓