Platform
Notifications
Persistent notification state, temporary feedback, preferences, and email delivery.
Announcements and Feed
Understand announcement-specific read confirmation.
Automation
Understand rule delivery outcomes.
Separate audiences
Administrative alerts use the Admin or Owner notification tray. Member notifications use the member drawer and notification page. A registration review alert never becomes a member notification, and audience-specific counts remain separate.
Persistent notifications and unread state
A persistent notification is stored until product retention removes it. It has its own unread state and can be marked read. Opening the tray or seeing another form of feedback does not itself mark that record as read.
Temporary toasts
Toasts report transient results and may also surface unread persistent notifications at session start. They disappear automatically or can be dismissed. Dismissing a toast changes only the temporary presentation, not the stored notification or unread count.
In-app and email delivery
In-app notification creation and email delivery are separate outcomes. Email depends on the notification category, member preference, community setting, recipient eligibility, available email configuration, and background processing. A successful in-app notification does not prove that an optional email was delivered.
Preferences
Members can manage supported announcement, event, birthday, and passport-reminder preferences. Community administrators control supported notification behavior and templates. Changing a preference affects future eligible delivery; it does not erase prior notifications.
Feature-specific read state
Announcement read confirmation and chat unread state are owned by those features. They may contribute badges, but they are not interchangeable with the general notification receipt. Follow the Announcements and Feed or Encrypted chat guide for those semantics.