Notifications overview

What Haubot notifies you about, where the notifications show up, and how to control them. A short tour before the per-channel articles.

Haubot sends you notifications when something on the platform needs your attention — a new bid arrived on your auction, a buyer requested access to a vault document, your password changed, a listing you follow got marked sold. The point of notifications is to keep you in the loop without asking you to constantly check the dashboard.

This article is the short tour: what we notify about, where notifications can be delivered, and the pieces you'll see in your settings page.

What kinds of events fire notifications

Roughly seven groups, all visible in your Dashboard → Settings → Notifications matrix:

  • Account security. Password changed, email changed, sign-in from a new device, OTP and email-verification codes, password-reset requests. The mandatory ones (OTPs, verification codes, reset links) always go to email — they're how you sign in or recover the account, so they can't be turned off.
  • Listings. A listing you posted got published, rejected by moderation, expired, or sold. A listing you're following changed state.
  • Auctions. A bid was placed (sellers), you got outbid (bidders), you won, you lost, an auction you're watching is ending soon.
  • UnitVault. Someone requested access to a private document on a listing you own. Access was approved, denied or revoked. A snapshot was created.
  • Direct messages. Someone sent you a message in the in-app inbox.
  • Network activity. Likes, comments, follows on your posts.
  • Reviews. You received a review, the seller responded to a review you wrote.
  • Platform announcements. Site-wide news, terms-of-service updates, policy and compliance notices.

The exact list, in the exact order they appear in your settings, is in Dashboard → Settings → Notifications.

Where notifications can be delivered

Four channels today:

  • In-app. The bell icon in the top-right corner. Always on for everything you have a subscription to. This is the canonical destination — even if every other channel is off, you can still see notifications by opening the bell.
  • Email. Sent from [email protected]. Default-on for important events (account security, listing state changes, auctions you're participating in). Off by default for low-signal events (likes, follows). Some events are mandatory on email (sign-in OTPs, verification codes) — those can't be turned off.
  • Discord. A webhook posts to a Discord channel you control. Useful for team notifications: every member of the channel sees them, so a seller's team can collectively watch new bids without each member needing to sign in. Read Connecting Discord for setup and the privacy considerations.
  • Telegram. A private 1:1 chat between you and our bot. Useful as a personal pager — fast, mobile-first, no team broadcast. Read Connecting Telegram for setup.

We may add SMS later for a small set of critical events. It's listed as "Coming soon" in the settings UI.

How the settings page is laid out

Two parts:

1. Connected channels (top of the page). Cards for each channel you can plug into — Discord, Telegram, and the always-active In-app and Email. Each card shows the connection's status (Connected, Pending, Failed, Revoked) and has Connect / Disconnect / Send test buttons. Email and In-app aren't really "connected" in the user sense; they ship out of the box.

2. Event matrix (below the channels). One row per event, one column per channel. The cell is a checkbox: tick to enable that event for that channel, untick to silence it. The matrix knows which events are forbidden for which channels (some Discord cells are locked because broadcasting to a team channel would leak account state; a few Telegram cells are locked because routing security codes to a chat would weaken your second factor). Locked cells show a lock icon and a tooltip explaining why.

What "default-on" and "opt-in" mean

Each event has a default for each channel:

  • Default-on — when you connect a channel for the first time, the cell is already ticked. Common for security events, listings you own, auctions you're participating in.
  • Opt-in — the cell is unticked by default. You only get the notification if you tick it. Common for high-volume / low-signal events (likes, follows, comments) and for everything via Discord (so connecting Discord doesn't suddenly broadcast a flood of past-week activity).
  • Mandatory — locked-on. Cannot be unticked. Used for OTP / email-verification / password-reset on the email channel — the things you need in order to sign in or recover the account.
  • Forbidden — locked-off. Cannot be ticked. Used for events the platform has decided shouldn't go to a particular channel (e.g., security codes via Discord — broadcasting to a team channel would defeat the second factor).

What you'll typically do here

Three common cases:

  • Right after signing up. Look at the In-app and Email columns. Defaults are sensible — you'll get account security and your own listings/auctions. If you don't want every email, untick a few rows in the Email column.
  • Connecting Discord for a seller team. Click Connect on the Discord card, paste a webhook URL from Discord, give it a label. By default the matrix only enables a small set of events for Discord (you opt in event-by-event). Tick the rows your team cares about — typically auctions, listings, reviews.
  • Connecting Telegram as a personal pager. Click Connect on the Telegram card, follow the deep-link, press Start in the bot's chat. Most events are default-on for Telegram once connected (it's a private chat — no team-broadcast concern). Untick anything you find too noisy.

What's next

  • Customizing your notifications — what each toggle does, how matrix decisions are remembered, how to silence everything quickly.
  • Connecting Discord — setup, broadcast acknowledgement, what's not routable to Discord, what to do if a webhook leaks.
  • Connecting Telegram — bot deep-link, what the bot replies, what's not routable to Telegram, disconnecting.