Notifications and Email
This chapter explains the company-scoped notification area in practical terms.
What belongs here
| Area | What admins usually do |
|---|---|
| email settings | maintain sender, routing, and delivery defaults |
| email logs | verify whether mails were sent and how they behaved |
| ticket systems | connect external escalation or support targets |
| alert templates | shape how alert notifications read |
| report templates | shape scheduled or generated report output |
Practical page matrix
| Page | What admins usually check | Typical next step |
|---|---|---|
| email settings | whether host, sender, and transport settings are correct | save, test, and then review status |
| email logs | whether delivery succeeded, failed, or was skipped | preview the rendered content and error state |
| ticket systems | whether escalation targets are connected correctly | verify ownership and routing intent |
| alert templates | whether alert wording fits operational expectations | compare against the actual alert audience |
| report templates | whether generated reports fit the intended recipients | review sample output and schedule context |
Typical working pattern
- confirm who should receive a notification
- check whether the right channel is configured
- test or review logs before assuming the alert logic is wrong
Typical warning signs
- connection tests fail after a save
- logs show
FAILEDorSKIPPEDinstead ofSENT - subject or rendered preview does not match the intended audience
- company-local email setup is confused with platform-wide defaults
Shared product context
For shared state, role, and visibility language, see Product Reference.