Kamzan ecosystem
Collect, get it signed, archive: without switching tools
Flow is not an island. The request starts from the client’s Files folder, the engagement letter is signed inside the flow with kSign, contacts land in Kontacts, and once the collection is closed the documents go back to Files with their structure.
Every hop between apps is a file that gets lost
Downloading from the portal, renaming, uploading to the archive, sending the PDF for signature with another service, copying the client’s email into the address book: these are the steps where a document ends up in the wrong folder. Flow is part of the Kamzan ecosystem and talks to the other apps: same users, same client companies, same branding. Integrations are switched on as extensions, only where needed, and every action respects the permissions of whoever performs it.
How it works
-
You start from Files
From the client’s Files folder you start an upload request: choose the flow, add the participants, and the collection is born already linked to that folder.
-
The client uploads and signs
Along the flow the client uploads documents and, at the signature step, signs the PDF with kSign without leaving the path. The signed document returns to the collection on its own.
-
You archive to Files
When the collection is closed and you archive it, Flow offers “Archive to Files”: choose where and under what name, and the documents move into the company archive with a folder per participant.
From request to archive, documents never leave Kamzan.
What you can do
-
Collection and folder linked
With the Files Link extension a collection stays tied to a Files folder: Flow managers opening the folder see the linked collections and how far along they are.
-
“Archive to Files”, when you decide
Archiving does not fire on every upload: you start it, once the collection is closed. Flow recreates the folder structure, keeps files encrypted and, if you wish, removes them from Flow. On Files the permissions of the person archiving apply.
-
Signing with kSign inside the flow
An engagement letter, a privacy notice, a form to sign: add a simple electronic signature step and the client signs right there. It needs the extension and a kSign subscription; each planned signature uses one credit, and unused ones come back.
-
Contacts that land in the address book
Every new participant becomes a contact in Kontacts, with nothing to copy over. And when you invite someone, you search the contacts the company already has.
-
One brand, the same client companies
Client companies are shared with the rest of the Kamzan ecosystem, and your company’s logo and colour appear on emails, the upload page and the participant portal.
-
Clear roles, encrypted files
Who can create flows, validate, coordinate, upload internally or view analytics is decided by the ecosystem’s user types. Received documents are encrypted in storage.
Frequently asked questions
Do documents go to Files automatically?
No, and that is by design: you start “Archive to Files” when the collection is closed, so only final documents reach the archive. You choose the destination folder and whether to remove the originals from Flow.
What kind of signature do the signature steps use?
kSign’s simple electronic signature. The signed PDF goes back into the collection next to the participant’s other documents. For advanced signatures or other methods, use kSign directly.
Does Flow connect to other software too?
Today Flow works with the Kamzan ecosystem apps: Files, kSign and Kontacts. To take data out there are CSV exports and the ZIP of the documents; there are no webhooks or public API.
Can whoever archives to Files put documents anywhere?
No: their Files permissions apply. In the picker they see only the folders they can reach, and moving the archive later also goes through Files’ rules.
The other Flow features
Simplify document collection with Flow
Request a demo: we’ll show you how Flow guides clients and suppliers to upload the right files.
Alex