Share a report with an auditor

Audit Hub gives the auditor reviewing your report their own way into Mangrove. You invite them by email, and Mangrove sends them everything they need to get in, so there is nothing for you to send separately and no files to email. They sign in, open the report you shared, and work through its batches, documents, and evidence in place. You keep control of who has access and can withdraw it at any time.

​

Inviting an auditor

Open the report in Reporting and find the Auditors card in the left column. On a report with no auditors yet, click Invite auditor. Once one is on the report, the card offers Manage instead, which opens the same dialog. Under Invite an auditor, enter their email address and click Send invite. An email address is all you provide. In the app, only account admins can invite or remove auditors. Over the API the check is on the token instead: any token with Accounting and Reporting write permission can do both, whatever role it belongs to. Treat those tokens accordingly. Mangrove emails the auditor a link to the specific report you shared. The invitation names the report, its value stream, and the production period, so the auditor knows what they are being asked to review before they accept. An auditor new to Mangrove fills in their name and chooses a password the first time they follow the link, then lands straight on the report. That first link is good for three days; if it lapses, Resend sends a fresh one, which invalidates the link sent before it. Anyone working from the old email has to use the new one. An auditor who already has a Mangrove login goes straight to the report, and their link does not expire. Inviting the same person again resends the invitation without creating a second grant, so Resend and a repeat invitation do the same thing. An auditor’s entry on the card shows where they are:

​

Removing and restoring access

Remove withdraws an auditor’s access to that report straight away. The next time they try to open it they get a message saying it is no longer available, and it drops off their list. Removed auditors move to an Inactive auditors section in the Manage auditors dialog, where Re-invite restores access for anyone whose own account has not been deactivated. Removing access to one report leaves any other reports you have shared with the same auditor untouched.

​

Previewing what the auditor sees

Preview auditor view opens the report exactly as the auditor gets it, inside a banner marking the preview. Use it before you invite anyone, particularly to confirm the documents and evidence you expect are attached.

​

What the auditor works with

The auditor signs in to Audit Hub and lands on a list of every report shared with them, across every account that has shared one. Opening a report gives them:

• A header with the reporting period, the report total, and the number of batches and documents included.
• Documents, Production batches, and Evidence sections listing everything included in the report.
• A preview pane. Selecting a batch shows its generated calculation workbook in place, and selecting a document or an evidence file previews that. Anything they can preview, they can download individually.
• Download Report Data (zip), which takes the whole package in one file.

Following a link from one workbook to another file in the package opens that file in a drawer, so an auditor tracing a figure back to its source stays inside the report. A link on an event opens a read-only view of that event instead of its CSV, listing the period and each reading with its correction history, so an auditor can see what replaced a value and which method produced it. Timestamps in the package and in the auditor’s view are rendered in the timezone of the account that produced the report, not the auditor’s own. The auditor’s own Profile page is where they update their name, email, organization, and password. Auditors have read-only access throughout. They cannot edit data, add comments, upload files, or change the report’s state. Mangrove records when an auditor first opens a shared report, so tell them their access is logged.

​

The report package

The package is the zip behind both the auditor’s inline previews and the download: Batch workbooks and evidence files are named after what you see in the app, with the record’s ID in parentheses, so a batch arrives as June-1-Biochar-Ledger_(ba_abc123def456).xlsx rather than under its ID alone. Spaces and punctuation become hyphens, which keeps the links between files inside the package working. Documents keep the filename they were uploaded with, and the archive itself is named for the project, the program, and the reporting period. Each batch workbook opens on its quantification model, then the batch output, then a sheet per model in the batch’s lineage, then a source data sheet per data point type. The source sheets carry the correction columns, so an auditor can see the reading as captured, what replaced it, which value the calculation used, and the method applied. Mangrove builds the package when you create the report, and rebuilds it when you add something the report includes. The auditor sees the rebuilt package, so anything you add while a review is under way reaches them without a fresh invitation. The download becomes available once the package is ready.

​

Over the API

Two endpoints manage access. Both need a token with Accounting and Reporting write permission, and both return 403 until Audit Hub is enabled on the account.

• Invite an auditor to a report
• Revoke an auditor’s access

Inviting is idempotent: sending the same address again resends the invitation rather than creating a second grant. Revoking addresses the auditor by email. Reading the roster, downloading the package, and everything the auditor portal does are in the Mangrove app rather than on the API.