On this page
Clouduxe raises alerts about invoices, services, security, and attacks on your servers. They appear inside the panel, and you choose which kinds reach you on which channel, including a Discord channel of your own.
Where notifications appear
Two places, both showing the same list.
The bell in the top bar of every panel page carries a badge with the number waiting, which reads 9+ once there are more than nine. Opening it shows the most recent alerts, each with its subject, a couple of lines of the message, and how long ago it arrived. It refreshes on its own while you have the panel open, and again each time you open it. View all notifications at the bottom takes you to the full page.
The Notifications page under Account lists the same alerts under the heading In-app notifications, with more of each message visible and the channel it arrived on tagged underneath. With nothing waiting, both read "You're all caught up".
How read state works on this list
Read state on this list is all or nothing.
Mark all read clears everything at once, which is what it says. Opening a single notification does the same thing: the row you opened stops being highlighted straight away, and the rest of the list is marked read as well the next time it loads. That is true in the bell and on the page.
Notifications are a copy of what is happening on your account, not the only record of it. An invoice is on Invoices whether you read the notification or not, and sign-in attempts are listed on Security and 2FA.
Delivery preferences
The Delivery preferences card decides what reaches you and how. The panel states the limit up front: "Choose how you'd like to hear about each kind of update. Security and billing alerts are always on."
It is a grid. Each row is a kind of update, each column is a channel it can be delivered on, and each switch is one combination of the two. A switch that is on means you receive that kind of update on that channel. Turning one off records an opt-out for that pair alone, so you can keep a kind of update coming on one channel while switching it off on another.
Most rows and the Email and In-app columns come from the billing system rather than from this panel, so which ones you see depends on your account. Two things in the grid are ours:
- The Discord column. It is only useful once you have connected a webhook, so its switch stays disabled until you do.
- The DDoS attack alerts row. This one is raised by Clouduxe Prism, not by billing, and it is described in full below.
Where a combination cannot be delivered the grid shows a dash rather than a switch. The dash means "this pairing does not exist", not "switched off". Billing topics do not go to Discord, and attack alerts do not go out by email.
- A row with a padlock beside its name cannot be switched off. Those are the alerts the card means by "always on", and their switches stay on and greyed.
- Save preferences is disabled until you change something. A save confirms with "Preferences saved."
- Saving writes the whole grid as it stands on screen, not only the switches you touched. If you have the page open in two tabs, the last save wins.
If the card shows "Delivery preferences aren't available right now. Try again shortly." in place of the grid, the panel could not load the channel list. Nothing can be changed until it loads, so reload the page, and open a ticket if it keeps happening.
DDoS attack alerts
When Prism starts filtering an attack on one of your servers, the panel tells you, and tells you again when the traffic returns to normal. You get one alert per attack rather than one per minute for as long as it lasts.
The alert names the address under attack. There is nothing to act on in it: filtering is automatic and already running by the time you read it. It exists so an attack is never the invisible explanation for a bad evening.
In-app alerts are on by default for every account. Turn them off with the In-app switch on the DDoS attack alerts row.
Sending alerts to Discord
The Discord alerts card connects a channel of yours to your account. Attack alerts and account notices are posted there as well as in the panel.
Create a webhook in Discord
In Discord: Server Settings > Integrations > Webhooks > New Webhook. Choose the channel you want the alerts in, then Copy Webhook URL.
Paste it into the panel
Paste the URL into the Discord alerts card and select Connect. The panel immediately posts a confirmation message to the channel, so you know it works before you rely on it.
Check it whenever you like
Test posts a sample alert to the channel. Use it after any change on the Discord side, such as deleting and recreating the webhook.
A webhook URL is a credential: anyone holding it can post into that channel. The panel stores it and never shows it again; the card only tells you whether a channel is connected. Replace swaps it for a new one, and the bin icon beside Test, titled Remove webhook, disconnects it.
Where email notices go
Email alerts go to the addresses on your account, and an address that has never been verified is the usual reason a notice does not arrive. Check Email addresses before you spend time on the grid above.
Related
Adding an address and getting it verified so notices reach you.
Security and 2FARecent sign-in activity, and what to do if something looks wrong.
InvoicesThe record that does not depend on you reading a notification.
Attack analyticsThe detail behind an attack alert: what was dropped, when, and on which port.