See documents across the workspace
The register at book level: what has arrived under no project, and which projects are missing something.
Files stay in your own storage. PadFlow holds the register, which is the record of what exists, what it says and what it is doing.
This page is that register at book level, and it leads with what is missing rather than with how much has been filed. A register that opens with a total tells you nothing you can act on. One that opens with what is unanswered does.
The inbox comes first
The inbox is what is on the register under no project. A document with no project is not lost, but it is not doing any work either, because nothing on a schedule can hang off a document nobody has said belongs to a deal. Say which deal each one belongs to and it joins that project's documents.
Under the inbox, one row per project names what is expected and not filed.
Where filing happens
Filing happens inside a project, because the folder a project keeps its documents in is a property of that project. This page tells you where to go. The project register is where the work is done.
Who can
- Documents at view or better: anyone who can read documents.
How to
- Documents with no project selected counts what every project is still waiting on.
- One row per project. A row opens that project's own register, where the gaps have names.
- The connection is workspace-wide and the folder is each project's own, so a run still happens inside a project.
Related pages
Known limits
The connection to a storage account is workspace-wide and is set up in settings. Without one, this page shows only what has been uploaded or recorded by hand.