Skip to content

Your notifications

The bell in the top bar, what puts things in it, and who else can see them.

3 min read

On this page

Where they are

The bell in the top bar carries a number when something is waiting. It is a control rather than a place: it opens the last few, and See all notifications at the bottom of it opens the full list, which is also Notifications in the sidebar.

Unread rows are marked three ways at once — a dot, a heavier title and a brighter body — so the list survives being scanned.

Opening a row marks it read and takes you to whatever it is about — the ticket, the quote, the booking. A row with nowhere to go, which most announcements are, just marks itself read.

What puts something there

Anything that happened without you doing it.

  • Support — Shipina replied to one of your tickets, or moved its status.
  • Billing — your Shipina invoice is ready, is overdue, or has been recorded as paid; your plan changed; a suspension was lifted.
  • Plan limits — you have passed nine-tenths of a limit, and again when the last one is used.
  • Quotes — a customer accepted or declined one in their portal.
  • Announcements — Shipina writing to every forwarder at once, usually about maintenance.

What is not there is anything you did. Marking a quote sent, recording a milestone, issuing an invoice: you were there, and an app that reads your own work back to you is one you stop opening. The same rule runs the other way, which is why your customers get notifications you do not — see below.

Everyone on your team sees the same things

A notification is addressed to a company rather than to a person, so a reply from Shipina reaches every staff account, and so does a plan-limit warning. That is deliberate: a message only the person who happened to open the ticket can see is one that goes unread while they are away.

The exceptions are the ones about a specific customer or partner, which go to that customer's or partner's own portal accounts and never to yours.

Read is per person, though. Marking something read clears it for you and leaves it unread for everybody else, because it is a record of what you have seen.

What your customers and partners see

Both portals have the same bell and the same list, carrying their own half of the same events:

  • a customer is told when you send them a quote, when a booking is confirmed, and when an invoice is issued, goes overdue or is settled;
  • a partner is told about the milestones and cancellations on the bookings they hold a slot on.

None of it is emailed. Shipina emails about accounts only — verification, invitations, password resets — so the portal is where their news lives, and the notification is what tells them to look. They never see anything about your plan, your Shipina invoices or your support tickets, and they never see an announcement: Shipina's relationship is with you, not with your customers.

Nothing to configure

There are no notification settings, on purpose. Everything addressed to you arrives, and the only thing you can do with a row is read it or mark the lot read. If that ever becomes too much, the answer will be a preference you set rather than a filter we guess at.

It keeps working when the rest of the app does not

While an invoice from Shipina is past due your workspace goes read-only: nothing can be created or changed until the payment is recorded. Your notifications are the exception. They keep arriving, you can still open them, and marking them read still works — which matters, because the notice explaining why everything else is refused arrives here, and a message you cannot clear is one you end up rereading.