--- title: "Notification history in Document360" slug: "notification-history" description: "Document360 keeps a history of all notifications pushed to any configured channels so members can better track what notifications have been sent or failed. You can view notification history in the Notifications History tab in the Notifications section in Settings. " tags: ["Notification channel", "Notification history"] updated: 2026-06-29T09:09:59Z published: 2026-06-29T09:09:59Z canonical: "docs.document360.com/notification-history" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.document360.com/llms.txt > Use this file to discover all available pages before exploring further. # Notification history **Notification history** in Document360 is a log of all notifications sent to your configured channels, showing delivery status, timestamps, and message details for each event. Use it to confirm that alerts reached their destination or to diagnose delivery failures across channels such as Slack, Microsoft Teams, Webhook, and SMTP. --- ## When to use notification history Review the notification history when you need to: - **Verify delivery** — Confirm that a critical alert (for example, a system update or content change notification) was successfully sent to the intended channel. - **Troubleshoot failures** — Identify why a notification did not reach a channel and take corrective action. --- ## How to view notification history 1. Navigate to **Settings** ()> **Knowledge base portal** in the left navigation bar. 2. In the left navigation pane, select **Notifications**. 3. Click the **Notification history** tab. The portal displays a list of all past notifications. ![Overview of notification history with details on submission and status for email channels.](https://cdn.document360.io/860f9f88-412e-4570-8222-d5bf2f4b7dd1/Images/Documentation/Notification%20history.jpg) --- ## Understanding notification history columns Each row in the notification history table represents a single notification event. The table includes the following columns: | Column | Description | | --- | --- | | **Channel name** | The channel through which the notification was sent (for example, Slack, Webhook, SMTP, or Microsoft Teams). | | **Status** | The delivery outcome — either **Success** or **Failure**. | | **Submitted on** | The date the notification event was triggered in Document360. | | **Sent on** | The date the notification was actually dispatched to the channel. | | **History** | Click **View details** to inspect the full email or message content that was sent. | --- ## Best practices - **Check notification history after configuring a new channel** to confirm that test notifications are delivered successfully before relying on the channel for critical alerts. - **Review failures promptly** — a **Failure** status may indicate an expired webhook URL, incorrect SMTP credentials, or a misconfigured Teams connector. Use **View details** to get the error context. --- ## FAQ **What channels appear in the notification history?** Notification history tracks deliveries across all configured channels, including Slack, Microsoft Teams, Webhook, and SMTP (email). Any channel you have set up under Notifications will have its delivery events logged here. **What does a Failure status mean and how do I fix it?** A **Failure** status means the notification was not delivered to the channel. Click **View details** in the History column to see the specific error. Common causes include an expired or incorrect webhook URL, invalid SMTP credentials, or a disconnected Microsoft Teams integration. Resolve the underlying issue in your channel configuration and verify with a new notification event. **Can I filter or search notification history by date or channel?** The notification history table shows all past notifications with their submitted and sent dates, allowing you to review delivery within a specific timeframe. Refer to the Document360 portal for any available filter controls on your current plan. NOTE Notification history is a read-only log. You cannot delete or modify individual notification records from this view.