Teams notifications
Automatic notifications give a short English summary of the outcome and any required next action. Human-request replies follow the human’s language preference. The Gateway agent handles questions and task routing; it is separate from the notification sender.
Configure the webhook in Settings → Teams notifications. A laser may inherit the common destination, override it or disable notifications. URLs remain in private service storage and are not written into card parameters or reports. Saving a destination does not enable a stopped notification service or send a test message.
Notification delivery, gateway requests and laser control have independent lifetimes. A queued notification is not proof of delivery, and a notification failure does not stop the laser lock. Unknown delivery is retained for inspection instead of being replayed.
Use the notification card and configured gateway references in the laser deck. Display labels describe their roles; stable routing IDs remain available in technical details. Existing archived records are preserved.