Email Reporting

Reports to the inbox.
No login. No seat.

Wevo pushes a report request form to authorised users by email. They adjust the parameters in the browser, click send, and the finished report returns to their inbox within seconds - generated from the pre-calculated cube on near-live data. Unlimited recipients, with no per-seat licence.

A request out,
a report back

No portal to learn, no seat to provision. The whole exchange happens in email and the browser, scoped to what each user is allowed to see.

  1. 1

    A request form is pushed by email

    On a schedule - a Monday morning, say - authorised users receive a pre-addressed email carrying a request form and a validation token. The catalogue lists only the reports their security profile allows.

  2. 2

    The user adjusts the parameters

    In the browser, they set the report parameters offered for that report - usually a subset of what they could otherwise access - then click send.

  3. 3

    Wevo validates and generates

    The token, the sender, and every parameter are validated against the user's profile. The report is generated from the pre-calculated cube on near-live data.

  4. 4

    The finished report returns

    Output is delivered to the registered user's inbox within seconds - and the whole request is audit-logged.

Email report request
StageWhereElapsed
Request form pushedInboxMon 07:00
Parameters set, sentBrowser+0s
Token + sender + profile checkedWevo+1s
Report generated from cubeWevo+4s
Report returnedInbox< 10s
Output formats: TXT · PDF · HTML · XLS · profile-scoped, audit-logged

Reporting for the people
you'd never buy seats for

A facility that's rare precisely because most tools meter every recipient. Wevo does not.

Unlimited recipients

There is no per-seat licence. Passive report consumers - budget holders, line managers, non-finance stakeholders - all receive reports without adding a penny to the licence.

Near-live data, in seconds

Reports are built from the pre-calculated cube at the moment of request - minutes behind the GL, not last night's batch. A late journal during close week is reflected without a re-run.

🔒

Secure by construction

Token, sender, and every parameter validated against the user's profile. Output returns only to the registered user, the catalogue is profile-scoped, and every request is audit-logged.

Precise scope,
always within the profile

For each hierarchy, a request can specify a node, a level pair, or both - and the result is always intersected with the user's security profile. A request can never widen access; it can only narrow it.

Node only

Only that node's data is reported - provided the node sits within the user's profile.

Level pair only

Only nodes within that level range that also fall within the security profile are reported.

Node + level pair

The children of the specified node, within the requested levels and within the profile, are reported.

Edge rule

If the upper level is lower than the level of the specified node, that node is not included in the report.

The full reporting picture

The Business Introduction sets out the reporting loop, the security model, and the parameter overlay in full - with diagrams and worked examples.

Start here Business Introduction The complete overview Concepts, architecture, the web interface, the email reporting loop, security, and deployment - illustrated end to end. ↓ Download PDF PDF · 28 pages Product Fact Sheet The four-page summary Capabilities, deployment models, and technical fit at a glance - for stakeholders and procurement. ↓ Download PDF PDF · 4 pages

See the loop
close in seconds

Request a demo and watch a report go out as a request and return to the inbox - scoped, validated, and built on near-live data.

Request a Demo See the Product