Keep important account changes visible in a private notice inbox

Notices, not a chat service

The Messaging workspace is currently focused on incoming system notices. It helps account holders review important events—such as password or contact-email changes and family learner profile or access updates—in one place. Each notice can be marked as read, and the account inbox shows what is still unread.

That boundary is deliberate. The current member experience does not provide direct messages, replies, or member-to-member conversations. Older direct-message records are retained, but the compose and reply routes have been retired; they should not be treated as an available feature.

Privacy at both ends

The member inbox shows notices associated with the signed-in account. On the support side, the administrative view summarizes total and unread notice counts by event category. It does not display account IDs or the notice bodies. This makes it possible to see whether notice activity exists without turning the support dashboard into a reader for private inbox content.

Notices are intended to explain an account event, not expose credentials. Password values are never included. Email delivery is a separate concern: an inbox notice should not be assumed to mean a corresponding email was sent. Email behavior depends on its own configured delivery workflow.

A simple review routine

Account holders can check the inbox when they review account settings and mark notices read after they have seen them. Support staff can use category totals to spot broad activity patterns, then follow the system's normal account-support process when a person needs help. If the inbox reports that setup is incomplete, the required registered database update needs to be applied before notices can be stored and displayed.

Messaging is therefore a focused account-notification surface—not a general-purpose team chat, customer support ticket queue, or email replacement.