Notifications, delivery and morning reports

Distinguish the feed from external delivery

The Notifications panel combines applicable console notices with selected activity history. Its Feed is a view of information available to your account. Preferences decide which of those items you see here. Email and webhook delivery are separate: administrators configure channels with their own families, severity floor and quiet hours. Hiding a family in your panel does not turn off its delivery channel.

The morning report is another distinct workflow. It is written and stored on its schedule, and can optionally be emailed to selected people. A report can exist without an email being sent. Conversely, receiving a notice does not mean the corresponding underlying issue has been resolved. Open the relevant record and inspect its present state.

Review and filter the account feed

1. Open the header's notification or activity control to show the Notifications panel, then choose Feed.
2. Use Search notifications and Filter notification type to narrow what is displayed. Increase the selected Last count when you need a wider loaded history.
3. Read the title, message, actor and time before following a notice to its source. Check that the destination is the record you intend to investigate.
4. Use Mark all read only when you intend to advance your read position for the loaded activity and console notices. It is broader than marking only the rows remaining after a local search filter.
5. If the panel says No matching notifications, clear search and type filters and review Preferences before concluding that no activity exists.

Save preferences for this account

Open Preferences and review Notify me about. Current families include Outages & recoveries, Physical & topology, Equipment relocations, UPS service & health, Lifecycle, Projects & tasks, Assignments & checkouts, Stock & reorder and General inventory changes. The descriptions help distinguish operational alerts from routine changes. Choose the families relevant to your responsibilities rather than treating every inventory edit as an incident.

Under In this panel, Show notifications here controls the panel display and Minimum severity filters lower-priority notices. Choose Save preferences to persist the choices. A save failure leaves the outcome unresolved; reload and check the stored preferences before assuming your next session will use the edited values.

Where the test-notification action is available, it creates an informational notice in Stock & reorder. The application explains when that test is hidden because the panel is off, the family is muted or the minimum severity excludes Info. This checks notice creation and account filtering. Any delivery channel that subscribes to Stock & reorder at Info will also email or post the test notice; that still does not confirm the channel works.

Ask an administrator to inspect the delivery channel

For missing external alerts, supply the notification, expected channel and approximate time. An administrator should inspect whether the channel is enabled, subscribes to the notification family and accepts its severity. Quiet hours can defer delivery in the channel's configured time zone; Critical notices skip quiet hours unless the channel sets a different bypass severity. Your account's panel filters do not explain these channel decisions.

Channel management requires structural administrator authority and the appropriate notification-settings page action. The console has no screen for delivery channels. An administrator with notification-settings access manages channels, their delivery history, health and tests through Cenovel's API.

A channel test is a real delivery to its configured destination. Confirm the recipient or endpoint and the purpose before sending it. A successful test confirms that particular attempt; it does not establish that every notification family is subscribed or that every future message will be delivered.

Interpret delivery outcomes carefully

Retryable failures use bounded retries and delays; permanent failures or exhausted attempts can be abandoned. Preserve the failure summary when escalating. Do not repeatedly create new test notices to compensate for a broken channel. Missing secret configuration or an unavailable service can prevent delivery even when the original notice remains visible in the console. Channel changes and tests are recorded in the audit log.

Scroll the table sideways to read all columns.

Understand saved reports and permission changes

A scheduled saved report is computed with the named person’s current access. Copies sent to an outside address or a notification channel use the schedule owner’s access and require that owner to retain Administrator EX authority. The stored copy keeps its original contents; a later retry does not rerun the query against newer data.

Before each delivery attempt, Cenovel checks whether the original report’s data scope is still permitted, whether the intended person or destination is still selected, and whether an included attachment is still permitted for download. A department change, removed recipient, changed email address or revoked access can cause the retained copy to be abandoned. Correct the access or recipient settings, then generate a new report if appropriate; an old copy is not redirected to a new address.

Morning reports with saved-view sections retain the original permission evidence for every included section. Losing access to one included section stops that entire retained copy from being delivered. Editing the current saved view does not change which permissions the older copy needs.

After upgrading to a release with these permission checks, previously queued saved-report copies without original permission evidence cannot be sent. Their retained contents are preserved until normal retention removes them. A newly generated report records the evidence needed for delivery.

Read and share a stored morning report

1. Open Outages, then Morning report. Check the report day and generation context instead of assuming the latest available report is today's.
2. Use Choose a day and Open report to revisit a stored report. A day without a report is reported explicitly; it is not replaced with another day's content.
3. Read coverage alongside outages and recoveries. Incomplete monitoring coverage is a reason to qualify the report, not a reason to describe the estate as fully checked.
4. Use Copy email text when you need to paste the stored report into a message. If browser copying is blocked, use the Text download where your permissions allow it.
5. Use Text or PDF for an export when Download is allowed. Keep the report day with the exported or copied content.

Configure report timing and email separately

Administrator EX can change the district morning report when the required report-page permissions are present. Its settings show Schedule, Report and email, the displayed time zone and the next-report status. Set Write the report at in the shown zone. Enable Email the report when it is written only when you have chosen the intended recipients.

People without an email address cannot be selected; correct their address under People first. Enabling email with nobody selected prevents saving. Review the Signature because it is used in the email, copied text and exports. Save and revisit the settings. If no mail server is configured, the report can still be written; email requires the mail configuration identified by Settings › Deployment › Mail.

A message that today's report was due but has not been written calls for checking the console worker and report configuration. The current application retains morning reports for 365 days. An old report removed by retention, a future day and a day never generated are different conditions.

Suppress planned maintenance without erasing evidence

Use Schedule maintenance for a monitored site, closet, switch, access point, server or address, and read what the drawer says the choice will quiet. Record Starts, Ends and the reason for suppressing alerts. The end must follow the start. A maintenance window is a planned coverage decision, not a declaration that the device is healthy.

Covered outages remain identifiable as Maintenance in site history, while the relevant alert, incident and morning-report views exclude them. Observations remain available. This distinction prevents planned work from appearing as an unplanned outage without rewriting the underlying evidence or presenting suppression as recovery.

If work finishes early, use Cancel on the window in Maintenance coverage and provide the Cancellation reason. Review the resulting outage view: an issue still open becomes visible again and its alert is sent once. Canceling maintenance does not repair equipment. Confirm the restored alerting context separately from the physical work and retain the reason for changing coverage.