A channel defines a reusable destination for authorized events. It does not itself determine when an event is generated or prove that a recipient received a message. Notification policy selects events and routing; templates define email content; SMTP supplies transport. These configurations require different checks.
Before you begin
Use a laboratory recipient or webhook you control and a role authorized to manage channels. Treat addresses and endpoints as sensitive where applicable. Do not use customer data to test an integration.
Procedure
- Open Notification channels and check whether an existing authorized destination can be reused.
- Create the channel with a recognizable label, offered type and required fields. Use protected input when credentials are needed.
- Confirm tenant and destination, save and reopen the record to verify permitted metadata.
- Use Test where available and send synthetic content. Check both the reported state and receipt in the laboratory system.
- Associate events, severity and recipients through the relevant policy. Review suppression, deduplication, escalation, digest and quiet hours when configured.
- For email, review the template and Email delivery separately. A content preview proves neither SMTP operation nor receipt.
- Generate a controlled event and compare Delivery history with the receiving system. Restore temporary policies when finished.
Verify the result
The channel remains saved, its test reports a consistent result and the destination receives the expected message or suppression is explained. Keep only a safe identifier and timestamp. Local acceptance can describe handoff to transport rather than final receipt.
Errors and recovery
If a message does not arrive, first check whether the event was generated and whether policy suppressed it. Then inspect destination, authentication and transport through safe messages. Do not send repeated tests while an outcome remains pending. Review consumers before deleting the channel.
Synthetic example
Create LabOperations with an authorized test mailbox. Send a synthetic notification, locate its state in Delivery history and confirm subject, text and links in the mailbox.
Verification scope
Use synthetic data and the role authorized for the task. Compare a visual confirmation with the saved record or relevant attempt. Retain only safe identifiers and messages for support; do not share secrets, personal information or tenant data. If an operation outcome is uncertain, check its state before repeating it.