Notifications

Notifications tell you when something relevant happens in your organization — a reply to your post, a response to your support ticket, a reward assigned to a student, and more. They appear as a badge on the inbox icon in Console’s header, with a dropdown list underneath.

How Notifications Reach You

1. Something happens in Console (a reply is posted, a ticket is answered, and so on).
2. The system decides exactly who should be notified about it — this happens automatically; you never see or filter irrelevant notifications.
3. If you’re currently online, the notification appears in your inbox dropdown immediately.
4. If you’re offline, nothing is lost — it’s saved for you and shows up as soon as you next open Console.

Note

Console only shows you the notifications waiting for you at the moment you connect — it doesn’t currently offer a way to browse your full notification history further back than that.

What Triggers a Notification

Who gets notified depends on what happened. Here’s the accurate breakdown:

Discussion replies

Action	Who gets notified
Someone replies to your post or comment	You — the person whose post/comment was replied to
Someone replies to their own post	No one — you never get notified about your own reply
Someone starts a brand-new discussion post (not a reply)	Every member of that channel, except the person who posted it

Note

Channels don’t have a separate “manager” role — just a creator and a flat list of members. A new post notifies all members of the channel, not a special subset.

Message replies

A reply in a message thread notifies the person who started the thread — unless they’re the one replying to themselves, in which case no notification is sent.

Support ticket replies

A reply notifies whoever is on the other side of the conversation — the ticket creator is notified when support or an admin replies, and support/the admin is notified when the ticket creator replies. Replying to your own ticket never notifies you.

Assigning a behavior or reward

Assigned to	What happens
An individual student	The student gets a notification that they earned it
An entire class at once	⚠️ No student is notified — this is a known gap, not intended behavior

Either way, the admin who made the assignment also gets a notification confirming their own action.

Sending an invite

The invited person isn’t a member yet, so they receive an email, not an in-app notification. The admin who sent the invite gets a notification confirming it was sent.

Creating, updating, or deleting things (classes, channels, assignments, behaviors, etc.)

Caution

This is the one most worth knowing: these actions only notify the admin who did it, as a confirmation of their own action. They do not notify other admins, teachers, or students. If you create a class, only your own notifications show “Class X created” — no one else’s inbox is affected.

Read vs. Seen

These look similar but track two different things:

Status	What it means	What triggers it
Read	You’ve opened/acknowledged the notification	Clicking it — this is what clears the unread badge count
Seen	A freshness indicator	Scrolling past it in the dropdown — shown as a green tick if just seen, yellow if seen in an earlier session

Seen status is just a visual freshness cue — it doesn’t affect your unread badge count, which is driven only by Read status.

If You’re Offline

You won’t miss anything. Notifications are saved against your account on the server, and the next time you open Console and reconnect, they’re delivered to you as a batch.