Download Reportworq
⬇ Guide PDF

The Workspace Inbox#

The Workspace Inbox is a mailbox built into Reportworq. Turn it on and Reportworq keeps a copy of every message it sends, viewable in the app through a dedicated Email Inbox screen that looks and behaves like a lightweight web mail client.

It runs alongside your real email provider. It does not replace one. That is what makes it useful in day-to-day operation, not just in a demo:

It is also the way to run Reportworq with no mail server at all. Enable the Workspace Inbox, leave the email provider set to None, and jobs run their full distribution path with every message landing in the inbox instead of the internet. That suits trials, demos, and training.

Previously called the "Demo" email provider. In earlier releases this was a provider you selected instead of a real one, so you could either send mail or inspect it, never both. It is now a checkbox that works with any provider. If you upgrade an install that had the Demo provider selected, the Workspace Inbox is switched on for you automatically and nothing is lost.

Turning it on#

  1. Go to Settings > Configuration > Email.
  2. Choose your Authentication Provider as normal: Basic, Microsoft 365 SMTP, Microsoft 365 Graph, or SendGrid. Or leave it on None if you do not want anything sent.
  3. Under Workspace Inbox, select Enable Workspace Inbox.
  4. Save the configuration.

An Email Inbox button (an inbox icon) appears in the top-right app bar. Selecting it opens the Email Inbox screen.

You do not need a real email provider. With the inbox enabled, Reportworq considers email configured, so distribution steps, notifications, and password-reset mail all work. They just land in the inbox instead of being transmitted.

How messages get captured#

You do not capture messages manually. Running work does it for you.

  1. With the Workspace Inbox enabled, run (or let a schedule run) any job or step that sends email, for example a distribution step that emails a report, or a burst that emails a report to many recipients.
  2. Reportworq builds the full email, stores a copy in the Workspace Inbox, and then hands it to your email provider for delivery, if one is configured.
  3. The message appears on the Email Inbox screen, newest first.

One copy per recipient. A captured message is stored once for each distinct recipient across the To, Cc, and Bcc lines. A report burst that emails three people produces three independent inbox entries, one in each person's inbox, just like real mail. Read and unread state and deletion apply per inbox, so marking a message read in one recipient's inbox does not affect the others.

Each entry keeps a complete copy of the original message (an .eml file) including all attachments, so you can open it, read the body, and download everything later.

Using the Email Inbox screen#

The screen is a two-pane, master and detail layout:

At the top right of the screen are Refresh, Clean inbox, and, for administrators, Clear all inboxes.

Read a message#

Select any row in the list. The message opens in the reading pane and is marked read automatically. The body renders as formatted HTML, with inline images shown in place, or as plain text, matching how the email was composed.

Download attachments#

In the reading pane, each attachment appears as a chip showing its file name, size, and a file-type icon.

Download the whole message#

To keep or forward the raw email, open the Actions menu and choose Download .eml. This saves the complete message, headers, body, and attachments, as a standard .eml file you can open in Outlook, Apple Mail, or any mail client.

Mark read or unread#

Two ways:

Delete a message#

Deletion asks you to confirm and cannot be undone. The message and its attachments are removed permanently.

Clean the inbox#

Clean inbox permanently removes all captured messages from the inbox you are currently viewing, attachments included. You are asked to confirm, and the action cannot be undone. The button is disabled when the inbox is already empty.

Refresh#

Refresh reloads the inbox list, which is useful after running a job in another tab so newly captured messages appear.

What you can do by role#

The Email Inbox is scoped to who you are.

Reader or author: your own inbox#

A reader or author sees only their own inbox, the messages captured for the email address they signed in with. There is no inbox picker, the list header simply shows your address. You can read messages, download attachments and .eml files, mark read and unread, delete individual messages, and Clean inbox to empty your own mailbox.

System administrator: every inbox#

A system administrator gets two extra capabilities:

Where it captures from#

The Workspace Inbox captures the same mail your email provider sends, so it works with the ordinary distribution flow:

The subject and body come from the same message template the real transport would use, so what you see in the inbox matches what a recipient would have received.

Limits#

A captured copy is not a delivery receipt. Reportworq stores the copy before handing the message to your email provider, so a message can appear in the inbox and still have failed to send, for example if the mail server was unreachable. Check the job log for the delivery outcome. The inbox tells you what was sent, not what was received.

Troubleshooting#

Symptom Likely cause What to do
No Email Inbox button in the app bar The Workspace Inbox is not enabled, or the page has not reloaded since it was In Settings > Configuration > Email, select Enable Workspace Inbox and save, then refresh your browser.
Ran a job but the inbox is empty The job step did not send email, or the inbox was not enabled when it ran Confirm the step is an email distribution, or a burst that emails, and that the Workspace Inbox was enabled during the run. Select Refresh.
Recipients are not receiving real emails, though the inbox has copies The Authentication Provider is set to None Set a real provider for actual delivery. The Workspace Inbox keeps working alongside it.
A message is in the inbox but the recipient never got it The copy is stored before the send is attempted, so the send may have failed Check the job log for the delivery error, then verify your email provider settings with Send test email.
A reader cannot see another user's messages Per-role scoping: non-administrators see only their own inbox This is by design. Only a system administrator can view other users' inboxes, via the inbox picker.
A burst to several people shows separate copies Per-recipient capture, by design Each recipient has an independent inbox entry. An administrator can switch between them with the inbox picker.

Feedback on this page

Comments, questions, requests, or something missing or unclear? Email us - the page you are on is filled in for you.

Email feedback on this page

Or write to support@reportworq.com directly.