docs: update notifications wording (#5030)
# What this PR does update notifications wording ## Which issue(s) this PR closes Related to https://github.com/grafana/oncall/issues/3104 <!-- *Note*: If you want the issue to be auto-closed once the PR is merged, change "Related to" to "Closes" in the line above. If you have more than one GitHub issue that this PR closes, be sure to preface each issue link with a [closing keyword](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests#linking-a-pull-request-to-an-issue). This ensures that the issue(s) are auto-closed once the PR has been merged. --> ## Checklist - [ ] Unit, integration, and e2e (if applicable) tests updated - [x] Documentation added (or `pr:no public docs` PR label added if not required) - [x] Added the relevant release notes label (see labels prefixed w/ `release:`). These labels dictate how your PR will show up in the autogenerated release notes.
This commit is contained in:
parent
b260a8e82b
commit
28526182a5
1 changed files with 6 additions and 6 deletions
|
|
@ -34,21 +34,21 @@ To configure supported messaging apps, refer to the following topics:
|
|||
|
||||
{{< section >}}
|
||||
|
||||
## Configure user notification policies
|
||||
## Configure user notification rules
|
||||
|
||||
Notification policies are a configurable set of notification steps that determine how you're notified of alert in OnCall. Users with the Admin or Editor role are
|
||||
Notification rules are a configurable set of notification steps that determine how you're notified of alert in OnCall. Users with the Admin or Editor role are
|
||||
able to receive notifications.
|
||||
Users can verify phone numbers and email addresses in the **Users** tab of Grafana OnCall.
|
||||
|
||||
- **Default Notifications** dictate how a user is notified for most escalation thresholds.
|
||||
- **Default notification rules** dictate how a user is notified for most escalation thresholds.
|
||||
|
||||
- **Important Notifications** are labeled in escalation chains. If an escalation event is marked as an important notification,
|
||||
it will bypass **Default Notification** settings and notify the user by the method specified.
|
||||
- **Important notification rules** are labeled in escalation chains. If an escalation event is marked as an important notification,
|
||||
it will bypass **Default notification rules** settings and notify the user by the method specified.
|
||||
|
||||
> **NOTE**: You cannot add users or manage permissions in Grafana OnCall. User settings are found on the
|
||||
> organizational level of your Grafana instance in **Configuration > Users**.
|
||||
|
||||
To configure a users notification policy:
|
||||
To configure a users notification rules:
|
||||
|
||||
1. Navigate to the **Users** tab of Grafana OnCall and search for or select a user.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue