A product by

Kamzan ecosystem

Signing starts where you are working and comes back where it is needed

A contract in a Files folder, a document collected with Flow, a PDF on your desktop: from each of these you can send for signature without downloading and re-uploading anything. The signer sees your company’s name and colours, and the signed document goes back to its place on its own.

Request a demo kSign overview

A signature should not force you to switch tools

Every time a document leaves the archive to be signed somewhere else, you end up with copies, wrong versions and folders to realign by hand. kSign is part of the Kamzan ecosystem: it works inside Files, Flow and Kamzan Desktop, notifies your systems when something happens and presents itself to signers with your company’s identity, not ours.

How it works

  1. Start from the document in front of you

    From a file in Files you choose «Send for signature», from Kamzan Desktop you drag a PDF, in Flow the signing step is already in the workflow. In every case the same kSign procedure opens, with the document already loaded.

  2. The signer recognises your company

    The invitation email, signing page and verification page carry your company’s logo, name and, if you enabled them, its colours: whoever receives the link knows at once who it comes from and trusts it enough to open it.

  3. The result goes back to its place

    The signed PDF goes back into the Files folder or Flow workflow it came from, webhooks notify your systems at every step and the «Pending signatures» widget reminds people what is still missing.

A document should not have to leave its place to get signed.

What you can do

  • «Send for signature» from Files

    From a file’s menu in Files you send the document for signature without downloading it. Once signed, the signed PDF and the event log return to the same folder, next to the original, and anyone with access to the folder finds them there.

  • Signing step in Flow workflows

    A document collection workflow can include the signature: the client uploads what is needed, signs along the same path and the signed document stays in the workflow, without a second, separate send.

  • Kamzan Desktop and «Pending signatures» widget

    Drag a PDF onto Kamzan Desktop and kSign opens with the document ready to prepare. In the other Kamzan apps the widget shows how many signatures are waiting for you, with the link to go and sign.

  • Signed webhooks

    kSign notifies an address in your systems when a request is sent, a signer signs or refuses, the request is completed or expires. Every call carries an HMAC SHA-256 signature, so the receiver knows it really comes from kSign.

  • Your company’s brand

    Logo, name, tagline and colours are set once for the whole Kamzan ecosystem, and kSign uses them on the signing page, on the verification page and in emails to signers.

  • Credits, users and user types

    One credit is worth one signature request, however many signers it has. The administrator allocates credits to people and reserves a share for signatures started from Files and Flow; user types decide who sees every request and who manages templates.

Frequently asked questions

Can we connect kSign to our management software?

Today the connection runs from kSign towards your systems: webhooks notify your software of sends, signatures, refusals, completions and expiries, so it can update the status of a case on its own. Creating signature requests directly from your software is not available yet: if you need it, let’s talk.

How do we check that a webhook really comes from kSign?

Every call carries in its header an HMAC SHA-256 signature calculated with a secret known only to you and kSign. Your system recalculates the signature on the content received and compares it: if it does not match, the call is discarded. On our side the secret is stored encrypted with your company’s key.

Can you sign directly from the «Pending signatures» widget?

No, and that is deliberate. Signing is an act with legal value: it requires the OTP code, explicit consent and recording in the event log, all of which happen on the signing page. The widget tells you what is waiting for you and takes you there in one click.

How are credits counted?

A signature request uses one credit, whether it has one signer or ten. Credits renew every month or every year, depending on the plan. The administrator can give each person a number of credits and reserve part of them for signatures started from Files and Flow, so one department does not use up everyone else’s.

Does the company branding also apply to emails?

Yes. Invitation, reminder, confirmation with the signed PDF and refusal notice go out with your company’s logo and name. The standard wording is available in several languages, and with kSign’s email templates you write your own, with placeholders such as the signer’s name and the document title.

The other kSign features

Sign your company documents with kSign

Request a demo: we’ll show you how kSign makes signing fast, compliant and non-repudiable.

Request a demo