OppenMailer

HomePricingDocsPrivacy
Sign inCreate workspace
Browse documentation

Getting started

Set up access, create a workspace, and learn the app shell.

Use this guide when you are opening OppenMailer for the first time, joining a workspace by invite, or handing the platform to a new operator.

Goal
Get signed in, land inside the right workspace, and understand the main operating surfaces.
Best for
Workspace owners, invited teammates, and anyone onboarding a fresh account.
Outcome
A working workspace context and a clear first-run sequence for the rest of the app.

Section 1

Account access

Create or recover access before you try to configure sending infrastructure.

Surfaces

Sign up · Login · Forgot password · Invite acceptance

How to use it

  1. 01Use Sign up for a brand-new account, or accept an invite link when another workspace owner has already added you.
  2. 02If you cannot get back in, use Forgot password first instead of creating a second account with the same email.
  3. 03After sign-in, confirm that your display name and workspace access look correct before you start operational setup.

Operator notes

  • OppenMailer is workspace-scoped. Your account can belong to multiple workspaces, but each workspace keeps its own settings, lists, templates, providers, and limits.
  • If you are invited into an existing workspace, start there instead of creating a duplicate workspace for the same team.

Section 2

Create or join a workspace

Workspaces are the operating boundary for your team and sending rail.

Surfaces

Workspace switcher · Create workspace · Invite acceptance

How to use it

  1. 01Create one workspace per team, brand, or sending operation that should stay isolated from others.
  2. 02If you already belong to more than one workspace, use the workspace switcher in the shell to move deliberately between them.
  3. 03Keep naming simple and specific so operators can tell production, testing, or client workspaces apart immediately.

Operator notes

  • Most app state is intentionally not shared between workspaces.
  • If something seems missing after a switch, first confirm you are still inside the intended workspace context.

Section 3

Learn the shell

The shell is split into build, operate, observe, and configure surfaces.

Surfaces

Overview · Lists · Templates · Compose · Campaigns · Reports · Notifications · Settings

How to use it

  1. 01Use Overview for the high-level pulse of the workspace: queue status, provider health, imports, and recent activity.
  2. 02Use Lists and Templates to prepare the inputs a campaign needs before you open Compose.
  3. 03Use Campaigns, Reports, Inbox, and Notifications after launch to operate the live system.

Operator notes

  • The sidebar can be collapsed on desktop if you need more room while working in denser screens like Templates or Reports.
  • Notifications are workspace-specific, so the bell and the Notifications page only show events for the currently selected workspace.

Section 4

Recommended first-run sequence

Set up the rail before you start writing campaigns.

Surfaces

Settings · Lists · Templates · Compose

How to use it

  1. 01Open Settings first and connect the provider, domain, sender identity, reply routing, and any warmup prerequisites you need.
  2. 02Import or create at least one audience in Lists so your campaign has a real target.
  3. 03Build at least one reusable template before opening Compose, especially if you need repeat sends or PDF attachments.
  4. 04Open Compose last, map the audience and template, then save or launch from there.

Operator notes

  • Trying to launch before the delivery rail is ready usually creates avoidable pauses or setup churn later in Campaigns.