Electronic Signatures on monday.com Forms: What Is Native

Published on September 14, 2026

A form that ends in “sign here” gets asked to do two different jobs at once. Whoever is building the form usually wants a simple acknowledgment: a box where someone draws their name to confirm they read a policy or agreed to a quote. Legal or compliance, if anyone asks, wants a real e-signature — timestamped, audit-trailed, tied to a verified identity, the kind DocuSign or a similar service produces.

Both monday.com’s own WorkForms and FormFlow ship a native way to capture the first kind. Neither one is the second kind. Here’s what each actually captures, and where the line to a dedicated e-signature app sits.

Quick answer

• WorkForms has a native Signature question type. The respondent draws a signature and it’s added to a Files column on the board as a PNG image, per monday.com’s own WorkForms question types  documentation.
• FormFlow has a Signature field that works the same way: signed with mouse, touchpad, or touchscreen, saved as a PNG to a file column, and can be marked required.
• Neither is a legally binding, audit-trailed e-signature. Both are drawn-image captures, suited to lightweight acknowledgment (agreements, consent forms, approvals) rather than contract-grade signing.
• Install FormFlow to add a signature field to your next form.

What WorkForms’ Signature Question Does

WorkForms’ Signature question type lets a respondent draw a signature directly on the form. On submission, monday.com saves it as a PNG image in a Files column on the board, per the WorkForms question types  support article. A few documented limits matter before you build around it:

• Not available on Subitems questions. If your form writes to subitems, you cannot add a Signature question there.
• Excluded from prefill. WorkForms’ URL and account-level prefill support a fixed list of question types (short text, long text, email, phone, numbers, dropdown, country); Signature isn’t one of them, so you can’t pre-populate it.
• Not preserved by Save as draft. A respondent who saves progress and comes back later finds the signature field empty and has to sign again, as covered in saving a monday.com form draft.
• Not editable through response editing. WorkForms’ Enterprise-only response editing, covered in monday.com Form Features by Plan, explicitly does not support editing a Signature question on a past submission — once it’s signed, that particular field is locked regardless of plan.

What FormFlow’s Signature Field Does

FormFlow’s Signature field captures the same kind of drawn image: the respondent signs with a mouse, touchpad, or touchscreen, and it’s saved as a PNG to whichever file column you map it to. It can be marked required like any other field, and the documented use cases are the same category as WorkForms’ — agreements, consent forms, approvals — not identity-verified signing.

Neither tool documents anything beyond the drawn-image capture: no certificate, no verified identity, no signing audit trail. If a signature only needs to show that someone with access to the form clicked through and drew something, either one covers it.

Side-by-Side

When a Drawn Signature Isn’t Enough

If what you actually need is a signature that holds up as evidence — a signed NDA, a client contract, anything where you’d need to prove who signed and when — a drawn PNG from either WorkForms or FormFlow doesn’t get you there on its own. That gap is a long-running request on monday.com’s own community: a 2018 feature request thread  asking for e-signature or DocuSign integration is still active, and a more recent thread  asks the same question directly.

Two documented paths cover that gap on the monday.com side:

• monday.com’s own DocuSign app , which connects a DocuSign account to a board so items can trigger a DocuSign envelope.
• Marketplace e-signature apps built specifically for monday.com, such as GetSign, which advertises audit trails and legally binding signing for contracts and agreements directly on monday.com boards — evaluate any such app’s own compliance claims before relying on it for a document that needs to hold up legally.

Neither WorkForms’ Signature question nor FormFlow’s Signature field is a substitute for that; they answer a different, smaller question (“did this person acknowledge this on this form”) rather than “is this a signed, provable legal document.”

Frequently Asked Questions

Is a WorkForms Signature question legally binding?

Not on its own. It saves a drawn image as a PNG to a Files column with no certificate, verified identity, or audit trail attached. For a document that needs to hold up legally, use a dedicated e-signature integration such as monday.com’s DocuSign app or a marketplace e-signature app.

Does FormFlow’s Signature field work the same way as WorkForms’?

Yes, mechanically. Both capture a drawn signature from mouse, touchpad, or touchscreen and save it as a PNG image to a file column. Neither adds identity verification or a signing audit trail.

Can I use a Signature question on a WorkForms subitem?

No. monday.com’s own documentation excludes Signature questions from Subitems forms.

Will a signature survive if a respondent saves a draft and returns later?

No, on either tool. WorkForms’ Save as draft explicitly does not preserve signature fields, and neither product documents a way to resume a saved signature.

Next Steps

• FormFlow field types, including Signature →
• monday.com Form Features by Plan →
• Save a monday.com form draft and finish it later →
• Install FormFlow and add a signature field to your next agreement or approval form.

Last reviewed: 2026-09-14. WorkForms’ Signature question behavior (Files column PNG storage, Subitems exclusion, prefill exclusion, response-editing exclusion) verified against monday.com’s WorkForms question types  support article. Community demand and monday.com’s own DocuSign app confirmed via community.monday.com  and monday.com’s DocuSign app  support article. Features may change.