Notification Preferences: One Switch, One Cadence, a Row per Event

The bell is not up for negotiation. Everything that happens on your records reaches the in-app bell, always, for everyone. /settings/notifications controls exactly one thing: which of those events also reach your e-mail inbox, and how often. Once that is clear, the page takes about a minute.

The master switch and the cadence

At the top sits e-mail delivery, on or off. Off means no notification e-mails at all, digests included, whatever the rest of the page says. Under it is one frequency for all of your mail: immediate sends each e-mail as the event happens, daily digest bundles the day into a single morning message, and off leaves you with the bell. One cadence for everything rather than one per event — a setting you understand beats forty you never touch.

A row per event type

Below that, every notification type the platform can send has its own row, grouped into Market, Auction, Pickups, Support, Billing & invoices and System. Each row is a single opt-out: leave it on and that type is e-mailed at your chosen cadence, switch it off and it stops arriving by mail while still reaching the bell. There is no channel picker per row and no urgency level. A type is mailed or it is not, and there is exactly one answer to when.

Sourcing has its own page

An ITAD bidding on customer pickup requests gets a different kind of traffic, so it gets its own page at /settings/sourcing/notifications, with the five events that matter there: a new match inside your coverage, a new pickup request published, your bid accepted, your bid rejected, and a request you bid on being awarded. It respects the master switch — when e-mail is off, or the cadence is set to none, the page says so and links you back rather than letting you toggle things that cannot fire.

And so does the customer portal

Trade-in portal users manage theirs at /trade-in/settings/notifications, in the same shape: one e-mail switch, one cadence, and rows for the events on their side — request published, approval requested, granted or declined, bids received and updated, award confirmed, pickup scheduled or completed, certificate ready. Their bell keeps working whatever they switch off, which is the point of putting the workflow in the portal rather than in their inbox.

In your language, not the sender’s

Every one of these e-mails is written in the language of the person receiving it: their account preference, otherwise their browser language, otherwise English. The German buyer gets German even when the operator who triggered the event works in Dutch. Preferences decide whether a message arrives. They do not decide what language it arrives in.

Save your changes

Your choices stay as a draft until you select Save. The save action and the unsaved-change status remain within reach as you scroll through the preferences. An unchanged form has nothing to save; after a failed save, your draft stays available so you can retry.