User settings and notification services
The per-user account settings and the notification-channel backends — the configuration that makes alerts reach a person.
Personal Settings
Section titled “Personal Settings”Personal Settings handles the account’s own settings:
- Change password — update the login password.
- Contact information — the email, phone, and messaging contact details that notification channels use to reach you — email, phone, and the messaging channels the product supports.
The user’s saved contact details are what the per-user notice types (Email and
the User/Robot messaging channels) resolve to when an alert fires — see
alerts-and-notifications.md for how a rule picks a notice and a notice picks
a channel.
Notification services
Section titled “Notification services”Configure → Notification Settings is where the channel backends are configured — the outgoing services a notice type needs before it can send.
Three backends ship: SMTP (email), and the WeChat and DingTalk service configs. Each needs its service credentials:
| channel | what to configure |
|---|---|
| Email (SMTP) | service name, SMTP server and port, encryption (SSL/TLS or none), mailbox account and password. With SSL or TLS the server’s certificate is checked, and STARTTLS is required, not attempted — see TLS for alert delivery |
| WeChat (work WeChat) | configuration name, enterprise ID (corpid), application ID, application key |
| DingTalk | the DingTalk app credentials |
These are the delivery backends. The channels themselves — which targets a
rule can actually use — are the notice types (User/Robot for the messaging
apps, plus the named Slack/PagerDuty/Teams/etc. channels shipped 11 Aug), each
with its own setup form. See alerts-and-notifications.md for the channel
list and the write-only-credentials note.