Files extension
The client’s thirty documents land in their folder, already checked
A loan file, an onboarding, a due diligence: dozens of documents to request from people who have no account. From the client’s folder in Files you open a Flow collection: whoever must deliver gets their list, uploads, a validator checks — and what passes appears in the Files folder, linked to the collection.
Files holds the archive, Flow collects
Flow is the Kamzan product for requesting documentation from external participants: flows of required documents, deadlines, validation, reminders. The extension hooks it to a Files folder with a wizard starting from the context menu: collection name and client; which flow — the list of documents the client must provide, defined once in Flow; options and deadlines; mode; validators — who checks the document is the right one; participants. From then on the folder shows the link to the collection, with one click opening Flow, and delivered and validated documents sit inside it, with the folder’s permissions. Whoever is not a Flow administrator sees the folder and the documents; the link is managed by those who have Flow.
How it works
-
Open the collection from the folder
Right-click → Request documentation: the wizard asks for name and client, the document flow, options, deadlines, mode, validators, participants. Seven steps, back and forth.
-
Participants deliver in Flow
They get the invitation, see the list of what is missing, upload document by document. No Kamzan account; reminders and deadlines are handled by Flow.
-
What is validated lands in Files
The validator checks; accepted documents appear in the linked folder, where they get permissions, versions and everything else Files offers. The link to the collection stays on the folder.
Requesting thirty documents is Flow’s job. Keeping them is Files’ job.
What you can do
-
Flows defined once
“Supplier onboarding”: company register extract, compliance certificate, policy, IBAN. Defined in Flow, reused for every supplier, without rewriting the list.
-
Validation before the archive
A wrong document does not enter the folder: the validator sends it back to the participant from Flow. The right one reaches Files.
-
Visible link
The folder shows the linked collection and opens it in Flow with one click. Archived collections no longer appear.
-
Files permissions
Documents that arrived are files of the folder: whoever sees it sees them, with levels, watermark, retention, everything.
Frequently asked questions
How is it different from File requests?
File requests are for Files members: one or a few documents, to colleagues with an account. Flow is for externals without an account, with long lists, validation and its own reminders. The “document request” link is the minimal version, for a file or two.
Do I need Flow?
Yes: the extension is the bridge, the collection is done by Flow. If Flow is not active, the entry does not appear.
Who can open a collection from the folder?
Whoever has the “Document collection” permission on the folder and a role in Flow. Managing the collection — participants, deadlines — stays in Flow, with Flow administrators.
The other Files features
Move your company files to the cloud
Request a demo: we’ll show you how Files makes storage and sharing simple and secure.
Alex