Report

To work with the report, navigate on the left hand side to the reports button (pencil button)

The editor opens on a paginated document seeded from the data room's risks, recommendations and document structure. A user can refine the narrative, restyle, manage versions and export to DOCX or PDF, while the underlying risk data stays live and in sync with all your work in Emma.

The editor opens from a data room's Report tab. First open. Emma generates a fresh document from the data room's current state: risks (with their levels, summaries, and recommendations), the document tree (areas, document types, documents), and cover-page metadata such as the client name, date, and any filters in effect.
​
The generator produces a fully structured document containing a cover page, areas as top-level sections, document types as subsections, risk tables sorted by severity, and recommendation blocks. During this phase the editor surface shows a skeleton (toolbar, sidebar, three A4 placeholders). Long reports with thousand files can take a few seconds to appear.

​Subsequent opens. The saved document is loaded and the live collaborative session reconnects. The document is not regenerated; edits, free narrative, image frames, and styling all persist as part of the report itself. To update for the latest report version, use Regenerate.

The editor has three regions:

Reports mix two kinds of content that behave differently. Understanding the distinction matters because edits to each propagate in different ways.

The editor treats both uniformly from a typing perspective: place the cursor and type. The difference is what happens behind the scenes (see Collaboration for how business-object edits propagate across surfaces).
​

A practical implication: if the user edits a risk summary in the editor, that change is visible in the risks tab of the data room and in the document viewer. If the user adds a paragraph of narrative between two risks, that paragraph lives only in the report.

Standard rich-text editing throughout the document.

​Text formatting (selection-scoped, applied via the toolbar or shortcuts):

Block styles (line-level):

Lists and alignment:
​
Bullet list, ordered list, align left / centre / right. Text-style marks like font family and colour are scoped to the selection, the same way Word handles them. Changing a heading style or alignment applies to the current line.

Pasting from external sources (Word, web pages, other Emma reports) preserves basic formatting where possible. Pasted content is mapped to the editor's block styles; styles without a direct equivalent fall back to Paragraph.

Risk findings, risk levels, and recommendations are surfaced as structured cells inside generated tables. The user interacts with them in three ways.

1. Edit the body text inline. Click into a risk-summary cell or a recommendation cell and type. Markdown formatting is preserved and the change is persisted to the underlying entity. While the cursor is inside one of these cells, the row is locked for other collaborators (see Live presence).

2. Use the inline action menu. A floating action menu opens from any risk row or recommendation row. It exposes:
​

3. Drive changes from elsewhere. A risk level changed in the data-room risk matrix or the document viewer is patched into the open report in place, with no banner (see Collaboration).

Risk tables are always sorted by severity (High, Medium, Low, Unspecified, No Risk). When a level changes inside the editor, the affected tables re-order and animate to their new position. When the same change comes from outside, the tables jump rather than animate, so the analyst notices that something shifted.

​

The cover page is fully editable like any other content. The generator emits five role-tagged blocks the user can recognise on sight:

Cover-specific typography (Eyebrow size, Title size and weight, Subtitle size and weight, Title tracking) lives in Styling, Typography section. Toggling Eyebrow or Jumbo on a cover line in the toolbar correctly clears the cover-role overlay so the change round-trips through DOCX export.
​

Typical edits on the cover page include replacing the auto-generated title with the deal codename, updating the date format to match the firm's house style, and adding a confidentiality line below the stats block.

Two ways to put an image on the page:

Once placed, an image frame supports:

Inline images flow with the text and reflow on pagination. Image frames hold their absolute position on the page and are well suited to cover-page hero images, watermarks, or floating illustrations alongside text.
​

Pagination is filter-aware: when filters hide content, page-break markers are hidden too, so the document never shows orphan empty pages.

Hierarchical table of contents under the outline tab:

Each area and document-type row has a chevron to expand or collapse. Click a row label to scroll the editor to that section. As the user scrolls the document, the matching outline row highlights and its parents auto-expand.

Each area and document-type row also shows risk-count badges on the right (red for High, orange for Medium, yellow for Low). When risk-level filters are active, badges for muted levels are dimmed.
​

Document rows reveal a small file-icon button on hover that opens the document viewer for that file directly. This is the fastest path from the report to the source PDF when the analyst wants to verify a finding mid-edit.

Filtered-out entries appear at 40% opacity and are not clickable. Empty state: "No sections found".​
​

The toolbar shows a live page counter (e.g. 3 / 12) on the right. It updates as the user scrolls. There is no go-to-page input; use the outline or scroll directly.

The toolbar Filters button opens a popover with three multi-select sections:

Filters combine as AND across sections and OR within a section. For example, selecting High and Medium in Risk Level plus Corporate in Areas shows risks that are (High OR Medium) AND in the Corporate area, etc.

Active filters are reflected in:

A Clear all link resets every filter. The Filters button shows a numbered badge when filters are active.
​

From the inline action menu on any risk row, View risk in document opens the document viewer on the risks tab with the matching risk pre-selected. This is the canonical way to jump from the report to the source evidence without losing the analyst's place in the report: closing the document viewer returns the analyst to the same scroll position in the editor.

The editor is real-time collaborative. Multiple analysts can edit the same report at the same time without explicit coordination.
​

Other editors' carets appear in the document with a coloured pointer and a name label. Selections highlight in the editor's colour for that user. Each connected user gets a stable colour for the duration of the session.

When another user is editing a specific risk or document-recommendation cell, the surrounding table picks up a subtle indigo overlay treatment to indicate the row is locked, so a second editor doesn't overwrite their work mid-edit. The lock releases as soon as the first user moves their cursor out of the cell.
​

Presence carries across surfaces:

The mapping today:

This prevents the classic split-screen scenario where two analysts overwrite each other while one is in the report and the other is in the document viewer.

The versions tab in the sidebar lets analysts snapshot the document and restore it later. This is the right tool for milestone snapshots (e.g. "draft sent to client 8 May", "post-call revisions").

A restore is destructive at the document level: it replaces the live document for everyone connected, not just the user who triggered it. There is no client-side offline cache to fall back on. Save a version before any operation you might want to undo broadly (a regenerate, a wholesale style change, a paste of new content).

The toolbar Styling button (palette icon and label) opens the styling dialog. Changes apply live to the open document. The dialog has seven tabs.

The header strip indicates whether the report uses the organisation template or has been customised:

A Save as org template action becomes available when the report has been customised, letting the analyst promote the current style as the new organisation default (see Saving as the organisation template).

​

A list of style presets. Each card shows the preset name in its own font, a tagline, and a six-swatch row (page background, text colour, High, Medium, Low, NoRisk).

Current presets:

Applying a preset clears inline text-style marks first, so the new font and colours take effect across the whole document. The logo, footer text, and per-page background overrides are preserved.
​

A Reset sizes link appears when typography is dirty.
​

Page-by-page background overrides come from the toolbar paint-bucket (see Pages), not the styling dialog. The default page background lives in Colors. The split is intentional: per-page overrides are a layout decision (typically applied to a single cover or divider page), while the document default is a style decision (applies everywhere by default).
​

The Save as org template action in the styling dialog header copies the current report's settings (typography, colours, table style, header and footer, logo, and so on) and stores them as the organisation's default. New reports generated after that point inherit the new template; existing reports keep whatever settings they were saved with.
​

This is the right path when one analyst has tuned a report to the firm's house style and the team wants future reports to start from the same baseline.

The toolbar Export button is a dropdown with two options:

Active filters are honored by the export (filtered-out content is excluded), as is the current pagination layout. To export a "full" report regardless of filters, clear the filters before exporting.
​

The button shows a spinner and a label like "Exporting DOCX…" or "Exporting PDF…" while the export runs, and is disabled until it completes.

A handful of recurring flows worth documenting end to end.