AI Troubleshooting for Industrial Networks User Guide

User roles and permissions

Updated: August 31, 2026

Want to summarize with AI?

Compare Admin and OT user access to alerts, AI chat, topology, inventory, settings, and user management.

AI Troubleshooting has two application roles: Admin and OT user. Your assigned role determines which pages, controls, and actions are available to you.

Access at a glance

Admin and OT user roles have different accesses and permissions over the features and capabilities of AI Troubleshooting for Industrial Networks.

Role-based access definitions


Area	Admin	OT user
Alerts and alert threads	View, investigate, manage, and mark alerts Resolved	View, investigate, and mark alerts Resolved
AI chat	Create threads and send curated freeform prompts	Use preset follow-ups in alert threads only
Topology	Search, navigate, configure, and edit	Search and navigate in view-only mode
Devices inventory	View and manage device records	View device records in read-only mode
Proxies inventory	View and manage proxy records	View proxy records in read-only mode
Custom fields	Add, edit, and manage fields and values	View available fields and values only
Settings	Access application settings and user management	No access

Permission-based access

OT users can investigate alerts, use supported follow-up prompts, and view Topology and Inventory. Only Admins can create independent threads, access Settings, or change device records and user access.

Note

If you have the OT user role, you might see New Thread, Ask a question, Discuss this device, Add devices, Custom field, or Remove without permission to use them. Inventory is view-only for OT users; Settings requires the Admin role.

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.