User roles and responsibilities in SR Ops

  • Versão de lançamento: Australia
  • Atualizado 12 de mar. de 2026
  • 1 min. de leitura

    • With user roles, you can grant users access to different parts of the SR Ops console. Roles determine the actions that users can or cannot perform in SR Ops.

    SR Ops has the following predefined roles:
    Tabela 1. Roles and responsibilities
    Roles Description Contains Roles
    sn_sro.sro_admin

    Administrators can manage account settings, configurations, and users.

    Administrators can perform the following actions:
    • Access, create, edit, or delete all configurations
    • Define and change user roles
    • Manage account settings
    • Set up and manage integrations
    • sn_sro.sro_manager
    • sn_sro.sro_user
    sn_sro.sro_manager Managers oversee a team of SREs. Managers assign SREs to the team on-call schedule, monitor their performance, create procedures to deal with incidents, and develop solutions. Managers ensure resilience across all the systems and the DevOps workflows.
    Managers can perform the following actions:
    • Define and setup and teams, services, and on-call schedules
    • Add and delete users
    		 sn_sro.sro_user

    sn_sro.sro_user

    An SRE that uses the SR Ops application to perform everyday tasks. Users are the individuals who are on call. They diagnose and remediate alerts and incidents in SR Ops.

    Users can only access the configurations that they are a part of. They can only access the alerts which they have permission for.

    SREs can perform the following actions:
    • Manage their profiles
    • Confirm their on-call schedules
    • Manage incident and alert records
    • Access the SR Ops homepage and dashboards
    An sro_user inherits the following roles:
    • cmdb_read
    • flow_operator
    • itil
    • app_service_admin