CloudReport: one daily digest of file changes across Dropbox, Google Drive and OneDrive

Updated 24 July 2026 · Archon Solutions

The problem CloudReport solves is narrow and extremely common: the drawing was updated, the revised specification was uploaded, the inspection report landed in the folder — and nobody outside the team that did it knows. Every provider has notifications, but they notify the wrong people at the wrong frequency.

What does CloudReport actually do?

CloudReport connects to the cloud storage you already have, compares each monitored account against its last observed state, and turns the difference into one readable email. The digest lists what changed and where, grouped by project and then by folder, with a link to each file at the provider where it already lives. Nothing is copied or re-hosted.

The design decision that shapes everything else is batching. One email per person per weekday morning is a fundamentally different product from one email per event. Per-event notification produces the inbox flood that makes people create a filter rule and stop reading — Microsoft 365 AutoSave alone can register one editing session as dozens of changes. A single morning digest is short enough to read on a phone on the way to site.

How does it work?

1. Connect the accounts over OAuth. An administrator signs in with Microsoft Entra ID and connects each Dropbox, Google Drive or OneDrive account with an OAuth grant. OneDrive and SharePoint document libraries are read through Microsoft Graph. You choose which folders are monitored — scoping to specific project folders rather than whole accounts is the safer option.
2. Add the recipients. Recipients are set per monitored account and identified by email address alone. There is no user provisioning, no invitation flow and no licence to allocate.
3. Receive the digest every weekday morning. Each recipient gets one email with a section per project, listing the changed files with links. Someone involved in four projects receives one email with four sections, not four emails.

Who is CloudReport for?

CloudReport is built for construction, logistics and project organisations — the sectors where the people who most need to know about a changed file are least likely to have a seat in the system holding it. That means site managers who need to know a drawing was revised before the crew builds to the old one; project managers tracking parallel projects; subcontractors outside the client's tenant entirely; and inspectors and client representatives who need visibility but no editing rights.

The common pattern is files spread across more than one provider: a company running Microsoft 365 for its own staff still receives material through a client's Dropbox and a consultant's Google Drive. CloudReport covers all three in one digest.

How is this different from the notifications the providers already offer?

Native notifications are per-event, per-provider and per-licensed-user, and those three limits are what make them insufficient for project work. Microsoft retired classic SharePoint alerts in July 2026, and the replacements — SharePoint Rules and Power Automate — send one message per event with no daily summary. In every case the person who needs telling must already be a licensed user of that provider, which excludes the subcontractors and inspectors who most need the information.

How does it compare with automation platforms and project portals?

Automation platforms deserve a fair hearing. Power Automate and Zapier can produce a daily digest: a flow that writes each change event to a store, a scheduled flow that reads and formats it, and logic that resets between runs. The cost is not the build — it is ownership, licensing once the solution outgrows standard connectors, and the handover when its author changes jobs.

What does CloudReport not do?

This section exists on purpose: most disappointment in this category comes from buying a notification tool and expecting a platform.

• It is not storage. CloudReport holds no file content, no previews and no thumbnails. Dropbox, Google Drive and OneDrive remain the system of record.
• It is not a document management system. There is no versioning, no approval workflow and no permission model of its own. A recipient who clicks a link still needs permission at the source provider to open the file.
• It is not a security or DLP audit tool. Products such as Netwrix and Varonis exist to detect exfiltration and anomalous access for an IT department. CloudReport tells a project manager that the drawing changed. Those are different jobs.
• It does not replace Dalux, iBinder or Interaxo. If you run a project platform, keep it. CloudReport covers the cloud storage that sits alongside it.
• It does not grant access. CloudReport never widens permissions in the source provider.

What happens to our data?

CloudReport stores metadata only: which accounts are monitored, file names and paths, change events, OAuth tokens and recipient email addresses. It stores no file content. The application and database run on Microsoft Azure in West Europe (Netherlands).

Two things are worth stating plainly rather than burying. File names are personal data and are sent in clear text in the digest. And storing no file content does not make CloudReport unable to read files — it holds OAuth tokens with read access, which is why minimal scopes and folder-level monitoring matter. Both points, and how this relates to the GDPR, NIS2 and third-country transfers under Schrems II, are set out on the security and data protection page.

Frequently asked questions