Unread Count and Marking Read
The toolbar at the top shows how many notifications are unread. Clicking any notification marks it as read and — if the notification has a destination link — takes you to that record (a deal, a transfer, an import result). Use 'Mark all as read' to clear the counter without opening each item.
Notification Types
Each item carries a small badge. Today three appear: Transfer (a branch transfer you requested was rejected), Refund (a refund approval is waiting for you, or your request was approved or rejected), and Reminder (something you scheduled for yourself). Deal, Payment, Import and Discount badges exist in the interface and will start appearing as those events are wired up. The badge helps you scan the list when there are many unread items.
What You See vs. What Admins See
Notifications are scope-filtered. Owners and admins receive notifications from every branch. Members with branch-scoped access only see notifications about records inside their assigned branches — a transfer rejection for a branch you don't have access to won't appear. This keeps the feed relevant and avoids leaking activity across branches.
How Far Back History Goes
The feed shows the most recent notifications paginated 20 per page. Older items remain available — page through to find them. There's no automatic deletion of read notifications; they stay in your history but with the unread dot cleared.
Common questions
- Why am I not getting email notifications?
- Because no operational event is emailed today. ShowOps currently sends email only for account matters — signup verification, password reset, and invitations — and for subscription billing. Everything else lives in this feed, so check here for activity. Email delivery for approvals, plus a once-a-day summary, is being built.
- Can I unsubscribe from a notification type?
- Not yet. Every event type relevant to your scope is delivered to this feed, and there is no per-type setting to turn one off. Per-type preferences are being built and will live in Settings.
- Does marking read affect anyone else?
- No. The unread status is per user. If a transfer is rejected, every recipient gets their own copy of the notification, and each person marks their own as read independently.