Date: Fri, 29 Mar 2024 11:55:15 +0200 (EET) Message-ID: <27793922.5883.1711706115706@jira.mcemcw.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5882_531966354.1711706115706" ------=_Part_5882_531966354.1711706115706 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The central target of the created alert scenarios is the EVALARM user. These are the ones who are responsible for the necessary ac= tions from the information prepared by EVALARM.
Users are divided into passive employees and activ= e users who are directly involved in the alerting process.=
To organize structured alert scenarios, EVALARM uses a role conc= ept for users, which regulates the different permission options. T= his ensures that the right users - and only those - have access to the info= rmation and actions.
In addition to the authorization, you can group users into individually = adjustable user groups to structure targeted alerting.
To fit the work plans to match the EVALARM users' needs, you can also cr= eate on-call groups. This function allows you to override = the volume profiles of phones and alert the members of the standby group in= case of an alert.
User management is divided into the following areas: