OppenMailer

HomePricingDocsPrivacy
Sign inCreate workspace
Browse documentation

Inbox and oversight

Handle replies, notifications, and admin-only visibility.

This guide covers the operational surfaces that sit beside campaign sending: Inbox, Notifications, and the admin dashboard.

Goal
Keep live conversations, alerts, and cross-workspace oversight organized without mixing them into content creation screens.
Best for
Operators monitoring replies, triaging workspace activity, or reviewing platform-wide state with admin access.
Outcome
A cleaner understanding of where to reply, where to read alerts, and where platform-wide oversight belongs.

Section 1

Use Inbox for live thread work

Inbox is where conversation handling belongs once recipients reply.

Surfaces

Inbox

How to use it

  1. 01Open Inbox to review thread status, read the timeline, and reply from the workspace context.
  2. 02Use the campaign context shown in a thread when you need to understand which send generated the conversation.
  3. 03Keep reply handling inside Inbox instead of treating notifications as the reply surface.

Operator notes

  • Inbox is authoritative for threaded communication. Notifications may alert you to an inbox event, but they are not the place to continue the conversation.

Section 2

Use Notifications for operator alerts and read-retention

Notifications is the alert stream, not the content workspace.

Surfaces

Bell dialog · Notifications page

How to use it

  1. 01Use the bell for a fast glance at recent unread workspace events.
  2. 02Open the Notifications page when you need filtering, search, mark-all-read, or read-retention cleanup controls.
  3. 03Keep unread items for things that still need operator attention, then mark them read once they have been handled or acknowledged.

Operator notes

  • Read-retention cleanup only removes read notifications. Unread items stay visible until an operator explicitly changes them.

Section 3

Use the admin surface for platform-wide oversight

Admin is not the everyday editing rail for a normal workspace operator.

Surfaces

Admin dashboard

How to use it

  1. 01Open the admin dashboard only when you need platform-wide monitoring, pooled infrastructure review, or oversight outside the current workspace.
  2. 02Keep routine campaign, list, template, and inbox work inside the workspace where it belongs.
  3. 03Use admin access deliberately because it bypasses the normal narrow operator focus of a single workspace.

Operator notes

  • If you do not have admin access, the normal workspace shell is the correct operating surface for nearly all daily tasks.

Section 4

Run a simple triage loop

Use a consistent response order when the workspace is busy.

Surfaces

Notifications · Inbox · Campaigns · Admin

How to use it

  1. 01Start in Notifications to identify what changed and what looks urgent.
  2. 02Move into Inbox for reply work, or Campaigns for send-state work, depending on the alert source.
  3. 03Only escalate into Admin when the issue clearly crosses workspaces or pooled infrastructure.

Operator notes

  • This keeps the admin surface from becoming a catch-all view for problems that are actually local to one workspace.