User Role Definitions

When you invite a user account to access Riverbed IQ Ops, assign roles according to the access that user needs. For Role-Based Access Control (RBAC Role-Based Access Control) across the product, how roles affect the UI, and how multiple roles combine on one account, see Role-Based Access Control. For every built-in role name and description, see Riverbed Console Built-in Roles.

The table below summarizes access by UI area using three capability levels. Match each level to users by assigning the appropriate combination of granular roles from those topics.

UI Area	Read access	Write access	Administrative access	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 the 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	✓	✓	✓