Skip to content

Reports · Staff

Inspect service evidence and delivery exceptions

Read current signal coverage without turning missing evidence into success.

Before you start

Staff/admin with authorized Operations access.

Steps

  1. Open Reports → Operations and note the displayed release and data source.
  2. Review available workspace reads, GroupMe state, email service events and authentication signals. Inspect any unavailable or partial coverage warning.
  3. Use Alerts for message exceptions and authorized provider diagnostics for delivery or sign-in issues. Keep credentials and recipient details out of public evidence.
Open the task page →

Check the result

You can identify recorded signals and gaps. A link request is not inbox delivery, a provider delivery event is not inbox receipt, and a sign-in event is not proof of portal arrival.

If something goes wrong

A zero or stale signal does not establish inactivity or healthy service. Synthetic service signals are preview data. No sender or authentication configuration is changed by reading this page.

Guide edition · October 22, 2026. Check your actual record after saving; a success message alone is insufficient proof. Contact program staff through your established channel and keep sign-in links private.