Skip to main content
Checked against the product · 2026-10-04

Emailed Reports — Admin Guide

Two Admin tabs decide what leaves Arcvue by email: Email Recipients — who gets which report — and Email Layout — what those reports contain and in what order. They are the only surfaces in the platform that push information out without anyone logging in.

The one thing to take away: delivery is a subscription, not a default. If nobody is listed for a report, that report reaches nobody, and nothing anywhere warns you about it.

For: administrators · Time: ~10 minutes · You'll need: the email addresses, and a decision about who should be told when a feed breaks.

How to access​

Admin → Email Recipients and Admin → Email Layout.

Part 1 — Email Recipients​

Each row is one person subscribed to one report:

ColumnHolds
NameDisplay name — required
EmailThe address — must be a valid address
RoleTheir role, chosen from a list
Report TypeWhich report this row subscribes them to
Entity FilterWhich part of the business they see
ActiveA toggle — on or off without deleting the row
ActionsEdit, delete

Three report types​

ReportWhat it is
Monthly PerformanceThe monthly numbers, scoped by the recipient's role and division — see Entity Filter below
Sync FailureAn alert that a data feed has failed
What's NewThe release notes for what shipped, filtered to the modules your tenant actually has

What's New is filtered to your tenant, not broadcast. One page serves every tenant, so each entry is tagged with the modules it belongs to and the sender drops the ones you do not have — an accounting-only tenant is never told about an FP&A screen. An entry with no tag is kept for everyone, because a platform-wide change applies to everyone and withholding it the first time somebody forgets a tag would look exactly like a month where nothing shipped. A heading whose entries were all filtered out is dropped with them, so nobody receives an empty section.

If the module set cannot be read, What's New sends nothing and records why. The comfortable-looking fallback — send everything — is precisely how a tenant gets told about screens it does not have, so it refuses instead.

Monthly Performance goes out when the books-closed date moves forward — and only for a month that is ready. Before it sends, Arcvue runs the report's own indirect-rate computation for the month. A month that cannot produce a fringe or an overhead rate yet, because the ledger it reads is still incomplete, is held, and the next scheduled run checks it again rather than mailing blank rates. Separately, if no Monthly Performance report has gone out for 45 days, the scheduler sends one regardless of the close date.

One person, one report, one row​

One dialog does both jobs and its heading is the mode: it reads Add Recipient when you are creating a row and Edit Recipient when you opened an existing one. A dialog headed Edit Recipient will overwrite the row you opened, so check the name before saving.

A row subscribes one address to one report type. Somebody who should receive both the Monthly Performance and What's New needs two rows — same name, same email, different report type. This is not a limitation to work around; it is what lets you give the same person a different Entity Filter per report.

The recipient form is a dialog, so Cancel is not the only way out — pressing Esc or clicking the dimmed area behind it does the same thing. None of the three saves anything, which is worth knowing before you experiment with a row you are unsure about.

Entity Filter scopes what they see​

CONSOLIDATED is the whole business and is the default. Narrowing it to a division is how a division lead receives their own numbers and only their own numbers.

The failure here is silence, not over-delivery. On Monthly Performance, who gets what is decided by role first, division second:

  • A recipient whose role is CEO, COO, CFO or CGO receives the consolidated report, whatever their Entity Filter says, with the executive brief written for that role — trimmed for a COO or a CGO the same way it is in the app.
  • Any other role receives their division's report — if a division is set. A division's report carries no executive brief: the brief speaks for the whole company, so it goes only to the four roles above.
  • Any other role with no division set receives nothing at all. The send is skipped, not defaulted. It is recorded with the reason, so the skip is visible in the delivery history rather than silent — but no email goes out.

That last case is the one to check. Arcvue will not guess whether a PM or an Analyst should see company-wide financials, because that is a decision about who may see them, so it records the gap instead of answering it in either direction. Set a division on those recipients.

Use the Active toggle instead of deleting​

The toggle deactivates a recipient without discarding the row. That is the right tool for somebody on leave, or a report you want to pause for a month — the configuration survives, so turning it back on is one click rather than a rebuild.

Delete asks for confirmation and names the person before it removes them. Reserve it for people who should no longer receive anything at all.

The trap on this page: sync failure is a subscription, not a guarantee​

Sync Failure is a report type like any other — which means if nobody is subscribed to it, a failing feed emails nobody. No warning appears, because from Arcvue's point of view an empty distribution list is a valid configuration.

When there are no recipients at all, the tab says so plainly: "Add a recipient to enable automated report delivery." Read that as: nothing is being delivered.

So make Sync Failure the first row you create on a new tenant, before the performance reports. Without it, a broken feed shows up only if somebody happens to open Operational Health — see Monitoring, Sync and Audit.

Part 2 — Email Layout​

Admin → Email Layout — the page's own heading reads Email Report Layout, so that is what confirms you are in the right place.

This is the shape of the emailed reports: which sections appear, in what order, and how much detail each one carries.

ControlBehavior
Drag handleReorder sections — drag to the position you want
Visibility toggleVisible — click to hide / Hidden — click to show
Detail levelHow much that section says — Full, Compact or Summary, in that order from most to least
Save LayoutCommits your changes
ResetBack to the default layout, with a confirmation first

Two reasons a detail level is grayed out, and only one is a setting​

A hidden section's detail level is disabled — reasonably, since a section nobody sees has no detail to tune. Make it visible first.

Some sections do not support a detail level at all. Hover it and the tooltip says so directly: "This section does not support detail level." That one is not something you can enable; it is a property of the section.

Checking which of the two you are looking at takes one hover, and it is worth doing before concluding the control is broken.

Saving​

The button tells you where you stand: it reads Save Layout while you have unsaved changes and Saved when there is nothing pending. Reordering and toggling change nothing until you save.

Reset​

Reset returns the layout to defaults and confirms first. If a layout has become a mess, this is faster and safer than dragging it back by hand. (The Re-seed Defaults tool on Setup & Repair also restores the email layout defaults — same result, reached from the maintenance side. See Period Locks and Maintenance Tools.)

Part 3 — When something looks wrong​

"Nobody is getting reports." Check Email Recipients is not empty, and check the Active toggles. An inactive recipient is configured and silent.

"A feed broke and nobody was told." Nobody was subscribed to Sync Failure. Add a recipient for it now.

"A division lead is seeing the whole company." Their Entity Filter is CONSOLIDATED. Narrow it on that row.

"I need one person on two reports." Two rows, one per report type. That is the design, and it lets you scope each one differently.

"I can't set a detail level." Either the section is hidden — make it visible — or the section does not support one. The tooltip distinguishes them.

"My reordering didn't stick." It was not saved. The button says Save Layout whenever there is something pending.

"The layout is a mess." Reset. It confirms before it acts.

One-line summary​

Delivery is a subscription, not a default — an empty recipient list is a valid configuration that silently delivers nothing, so create the Sync Failure recipient first or a broken feed will notify no one. One row is one person, one report type, which is what lets you scope the same person differently per report; use the Active toggle rather than delete to pause somebody. On Email Layout, drag to reorder, toggle visibility, and remember that a grayed detail level means either hidden or unsupported — the tooltip tells you which. Nothing takes effect until the button stops saying Save Layout.