Native E-Signature

What this does

Lets a user sign a Quik! form directly in the Form Viewer by drawing their signature on screen, with no third-party e-sign vendor involved. Quik! walks the user through each signature field in role signing order, then converts the completed form into a locked PDF.

When to use this

Use Native E-Signature for simple, low-risk signing: acknowledgements, internal sign-offs among employees, or sales orders. It exists for the cases where a full e-sign vendor is more cost or complexity than the job needs.

Do not use Native E-Signature for financial transactions, healthcare data subject to HIPAA, or anything that requires a higher level of security or compliance with privacy laws. Native E-Signature is an electronic signature only. It is not a digital signature backed by certificates or a private key infrastructure. For those cases, use DocuSign or SIGNiX. See E-Signature Options for the comparison.

Before you start

You need:

• The Sign button enabled in the Form Viewer. See Customizing the Form UI.
• A Quik! OAuth Bearer token. See Authentication.

How to enable

Set the e-sign type to native when you generate the form. With the Sign button showing, this routes it to Native E-Signature instead of DocuSign or SIGNiX.

REST request:

"ESignType": {
  "Type": "nativeESign"
}

How signing works

When the user clicks the Sign button:

1. The viewer scrolls to the first page that needs a signature, following the role signing order set by the Quik! Field Definition.
2. The user draws their signature on screen, or chooses to skip that field.
3. Clicking Done advances to the next signature field.
4. The process repeats until every signature field is signed or skipped.
5. The completed form is converted into a locked, non-editable PDF.

On-screen indicators

• Signature fields show a yellow background with the text "CLICK TO SIGN".
• The page thumbnails on the right show a triangle in the corner: green means signed, yellow means a signature is still needed, red means the user submitted before completing a required signature.

Device and browser support

Native E-Signature works across modern desktop and mobile browsers, including iOS and Android phones and tablets, and current versions of Chrome, Edge, Firefox, and Safari.

Pitfalls

• Not for regulated or financial use. This is an electronic signature with no certificate backing. If compliance or auditability matters, use DocuSign or SIGNiX.
• The signed PDF is locked. Once signed, the form becomes a non-editable PDF. Capture any data you need before signing, not after.
• The Sign button must be enabled first. If the Sign button is not configured to show in the viewer, there is nothing to launch Native E-Signature.

Related articles

• E-Signature Options. Compare Native E-Signature with DocuSign and SIGNiX.
• Roles and Role Prefixes. How signing order is determined.
• HTML vs PDF Execution. Understand the document output that gets signed and locked.