Notifications
ProxCenter can send notifications when important events occur in your infrastructure -- alerts firing, backups failing, tasks completing, or compliance scans detecting issues. Notifications are delivered via email or webhooks.
Overview
Notifications are triggered by events in ProxCenter. You configure notification channels (where to send) and then associate them with the event types you care about. Multiple channels can receive the same event, and each channel can be filtered to only specific severity levels.
Notification Channels
Email
Send notifications to one or more email addresses. ProxCenter uses SMTP to deliver emails.
| Field | Description |
|---|---|
| SMTP Host | Your mail server address |
| SMTP Port | Port number (587 for STARTTLS, 465 for SSL, 25 for plain) |
| Username | SMTP authentication username |
| Password | SMTP authentication password |
| From Address | The sender email address |
| Recipients | Comma-separated list of recipient email addresses |
| Use TLS | Enable TLS encryption |
Webhooks
Send notifications as HTTP POST requests to any URL. The payload is a JSON object containing the event type, severity, message, and metadata.
| Field | Description |
|---|---|
| URL | The webhook endpoint to receive POST requests |
| Headers | Optional custom headers (e.g., Authorization: Bearer <token>) |
| Secret | Optional shared secret for HMAC signature verification |
Webhooks integrate with:
- Slack -- Use an Incoming Webhook URL
- Microsoft Teams -- Use a Teams Incoming Webhook connector
- Discord -- Use a Discord webhook URL
- PagerDuty -- Use the Events API v2 endpoint
- Custom systems -- Any HTTP endpoint that accepts JSON POST requests
Event Types
| Event | Description |
|---|---|
| Alert triggered | A threshold alert has fired (CPU, memory, storage, etc.) |
| Alert resolved | A previously triggered alert has returned to normal |
| Backup failed | A backup job failed on a connected PBS or PVE instance |
| Task failed | A Proxmox task completed with an error |
| Node offline | A Proxmox node has become unreachable |
| Connection lost | A ProxCenter connection to a Proxmox instance is down |
| Compliance issue | A compliance scan found new critical or high findings |
| CVE detected | A CVE scan found new critical vulnerabilities |
Configuration
- Navigate to Settings > Notifications
- Add a notification channel (email or webhook)
- Test the channel using the Send Test button
- Select which event types should trigger notifications on this channel
- Optionally set a minimum severity level to reduce noise
Start with critical events only (node offline, backup failed, connection lost) and expand as needed. Too many notifications lead to alert fatigue.
Notification channels are available in the Enterprise edition.
Broadcast Messages
Notification channels push events outward. A broadcast message does the opposite: it shows a banner inside ProxCenter itself, to announce a maintenance window or any other message that every affected user should see before they start working.
Broadcast messages are managed in Settings > Broadcast. The tab is provider-only: it appears for a super administrator working in the provider tenant and holding admin.settings.
Unlike notification channels, broadcast messages are not gated by a licence feature. They are available in both editions.
Creating a Message
New message opens a dialog with a live preview of the banner:
| Field | Description |
|---|---|
| Message | The text shown in the banner, up to 500 characters. It is displayed as plain text, never as markup |
| Background colour / Text colour | Free colour pair, with one-click Info, Warning, and Critical presets. There is no separate severity field: the colours carry the severity |
| Starts at / Ends at | Optional scheduling window. Leave both empty for a message that shows until you disable it. An end must be later than a start |
| Audience | All users, Selected tenants, or Selected roles |
| Users may dismiss this banner | Whether the banner carries a close button |
| Active | Whether the message is published at all |
Keep the contrast readable. The dialog warns when the colour pair falls below the 4.5:1 accessibility ratio, which is easy to hit with a light text colour on an amber background.
The message list shows each message with its audience, its window, and a state chip:
| State | Meaning |
|---|---|
| Active | Enabled, and inside its window if it has one |
| Scheduled | Enabled, but its start date is in the future |
| Expired | Enabled, but its end date has passed |
| Disabled | The Active toggle is off |
Creating, editing, and deleting a broadcast message is recorded in the Audit Log.
Choosing an Audience
| Audience | Who sees the banner |
|---|---|
| All users | Every signed-in user |
| Selected tenants | Users working in one of the selected tenants. A provider administrator who switches into a targeted tenant sees it too, because the match follows the tenant currently in use, not the account |
| Selected roles | Users holding one of the selected RBAC roles in the tenant they are working in |
What Users See
The banner is fixed to the top of the interface, above the header, on every page of the dashboard. It is not shown on the login page. Several active messages stack, in which case the layout shifts down to keep the whole interface reachable.
ProxCenter refreshes the active messages about once a minute, so a banner appears and disappears on its own without anyone reloading the page. The scheduling window is evaluated with the server clock, not the browser's.
A dismissal is remembered per browser, not per account. The same user sees the banner again in another browser, in a private window, or after clearing site data. Editing a message also brings it back for everyone who had dismissed it, which is convenient for correcting a maintenance window but surprising for a cosmetic edit. Deleting a message removes the banner immediately for every user.
A banner published without Users may dismiss this banner has no close button and cannot be hidden. Reserve it for messages that must stay visible for the whole window.
Permissions
| Permission | Description |
|---|---|
settings.manage | Required to configure notification channels and rules |
admin.settings | Required to create, edit, or delete a broadcast message, together with super administrator rights in the provider tenant |