Vai al contenuto principale

The notification centre

The bell keeps a record of everything Nose told you in this stable — including the messages you never received, because it is not a channel.

In questa pagina

Nose has always been able to tell you things — a ride you were added to, a cancellation, a top-up that failed. Until now it had no memory of having said any of it: a push notification you dismissed was gone, and an email lives in your inbox rather than in the app. The notification centre is that memory. Everything Nose told you in this stable is listed there, oldest still visible until it ages out, whether or not any message ever reached your phone.

Where to find it

  • On a computer — the bell at the top of the left-hand rail. It opens a panel over whatever page you were on, so you don't lose your place. A dot on the bell means you have something unread; it never shows a number.
  • On a phoneMoreNotifications. It's a normal page, so the back button and a shared link both work the way you'd expect.
  • On the dashboard — there's a Notifications tile you can add from the widget catalogue, showing your newest unread items. It isn't there by default; add it if you want notifications in your morning glance.

Each stable has its own list. If you belong to two stables, opening the bell in one shows only that stable's notifications — the same way everything else in Nose is scoped to the stable you're in.

Reading a notification

A row says what happened, where it lands, and how long ago it was. Selecting it takes you to the thing itself — the ride, the request, your wallet — exactly as tapping the push notification would have.

There are no buttons on the row beyond that. Confirming a request or cancelling a ride still happens on the page that owns it, not in the list.

Read and unread are yours to set

Every row has a marker on the right: a filled dot while it's unread, a hollow ring once you've read it. Select it to flip it, in either direction, as many times as you like.

Nothing marks itself read. Opening the bell, scrolling past a row, or even following it to the ride changes nothing — the only thing that marks a row read is you pressing that marker. That's deliberate: leaving something unread is how you keep it in front of you until you've dealt with it, and an app that quietly cleared the list when you glanced at it would take that away.

Marked read means "out of my default view", never "deleted". The list has two tabs:

  • Unread — where you start, and what the bell's dot counts.
  • All — the full history, including everything you've already read. Anything here can be marked unread again, which puts it straight back in your Unread tab.

Mark all as read clears the tab you're looking at in one go, and offers an undo for a few seconds afterwards. The undo restores exactly the rows it changed — nothing you'd read earlier by hand is affected.

Why muted notifications still show up here

This is the one that surprises people, so it's worth being precise.

In your account settings you choose how Nose reaches you: push, email, and a switch per kind of message. Those settings govern delivery — whether your phone buzzes, whether an email is sent. They do not govern what the app remembers.

So if you switch off ride reminders, no reminder is pushed or emailed to you — and the reminder still appears in your notification centre. That's the intended behaviour, not a leak: you muted the interruption, not the record. The alternative would be an app that has no idea a ride was cancelled because you'd once turned a switch off, which is the exact problem this feature exists to fix.

Put the other way round: the notification centre lists everything addressed to you. Push and email each show a subset of that, according to your settings. A message that reached your phone always has a row here; a row here often has no message behind it at all.

The bell and the badges are not the same signal

Staff sometimes see two markers for one event — a dot on Requests in the navigation and a dot on the bell. They mean different things and clear differently:

  • The navigation dot is queue state: there is work waiting. It clears when the work is done, by whoever does it.
  • The bell is your event log: you were told something. It clears when you mark it read, and only for you.

A colleague confirming a request clears the first for the whole team, and leaves the second on your bell until you've seen it.

Good to know

  • Notifications don't stay forever. Read ones are cleared out after about three months; unread ones are kept about twice as long, and are never removed while they're still unread and inside that window. Nothing you deliberately left unread disappears out from under you.
  • The list is your own. Nobody else can see it, and marking something read doesn't affect anyone else's view.
  • Not every kind of message writes a row yet. The first release covers requests, ride changes and cancellations, ride reminders, top-ups and billing; horse changes, series changes and boarding messages follow later.
  • Your notifications are part of the data you can export, and they are deleted along with your account.

Related

  • Your account — the push and email settings, and what each kind of message is.
  • Export my data — download a copy of everything Nose holds about you.
  • The dashboard — where the notifications tile can live.
The notification centre · Horsenose