Service operations / communication

monday WorkForms File Upload Not Working? Check the Form, Role, and Destination

Troubleshoot missing upload fields, login prompts, blocked attachments, and missing board files in monday WorkForms without opening access unnecessarily.

The short answer

Find the first stage where the photo is missing: question shown, attachment selected, submission recorded, file in the intended column, or authorized recipient able to open it. For a workflow configured to create board items, check the expected item too. These are separate receipts, not a native diagnostic feature or a promise that each step happens automatically.

Start with the existing request before asking the customer to send another copy. A missing question, a login restriction and a technician's shared-view limitation need different checks. This guide proposes a harmless-file investigation; no live upload, account access or successful recovery was tested.

Check the question before the transfer

monday's question-types documentation maps Upload file to a Files Column. Adding a board column does not automatically add a form question. Add content can connect an existing column, while an unassociated question may create another column. Inspect the exact question label, whether it is hidden or required, and its association rather than assuming the visible board column is the destination.

Conditional-logic documentation says prior responses can determine which question appears. Reproduce the intended branch with harmless answers. If the photo question never appeared, that is a visibility or configuration question before it is a file-transfer question. Changing an association now does not prove an earlier missing file has been restored.

Record the actual audience and session

WorkForms settings and permissions places Require login under Share form and Sharing permissions, restricting that mode to account team members. Viewers cannot upload. For signed-in member or guest cases, administrator upload and download settings matter; a submitter lacking upload permission may be unable to submit a form containing a file question.

Record the signed-in person's actual role. Do not label a signed-out external respondent Guest or Viewer by assumption. For that external context, reproduce the intended sharing policy with harmless data and escalate if its permission path is unclear. The authorized owner should choose the smallest justified correction, rather than blanket guest access, a public board or removal of required login.

The sharing and results guide describes direct links, embedding and the Results surface. An administrator's successful preview is not proof that the customer's actual direct link or embed works. Write down which surface and session you are checking, keeping private links out of a public support post.

Use the symptom to choose the next evidence

Symptoms: next evidence and the inference to avoid
CheckRecord or next decision
Photo question absentCheck that the question exists, its hidden setting, branch and mapped column. A board column alone does not prove a form question exists.
Login promptCheck intended audience and Require login policy. A prompt is not automatic justification for removing protection.
Cannot attach or submitRecord actual session, role if signed in and exact error. Ask the authorized administrator to inspect relevant permissions; preview success does not settle this case.
Previously selected photo gone after resumeCheck whether a draft was resumed. Do not infer deletion of an already submitted file.
Submission recorded, target blankReconcile response, item-creation setting, expected board/group/item and question mapping. Mapping is a hypothesis, not a recovery guarantee.
Office opens photo, technician shared view cannotIdentify the recipient surface and authorized handoff. Do not make the board public to treat a downstream visibility issue as an upload defect.

The getting-started guide says public shared forms can accept responses without an account, subject to restrictions. Save as draft does not preserve files or signatures. That can explain why a resumed draft needs file selection again; it does not diagnose an actual complaint or establish deletion of a submitted attachment.

The settings guide also permits item creation to be disabled. A form response and a board item are therefore separate things to reconcile. Before calling a blank board column a failed submission, check whether this form was configured to create the item you expected.

Files Column documentation says files are not visible or downloadable in shared board views. That specific surface limitation does not prohibit public form uploads, nor establish that Shareable boards or invited guests universally cannot access files. Identify the actual handoff surface before deciding what is missing.

Copy a small incident record

Use one incident ID and a harmless PNG or JPG for any approved proposed recheck. Record its actual size; this guide makes no universal WorkForms size guarantee. Leave the result blank until observed. Keep customer photos, private file URLs, tokens and invitation details out of this public example.

WorkForms incident worksheet: blank original record
FieldYour entry
Case ID and authorized investigation owner____________
Intended audience and access policy____________
First observed missing stage____________
Direct link or embed____________
Signed-out external context or actual signed-in role____________
Question label and mapped column____________
Draft resumed: yes / no / unknown____________
Harmless filename, type and actual size____________
Submission reference, time and time zone____________
Item-creation setting____________
Expected board, group and item if applicable____________
Authorized owner sees file: evidence or unknown____________
Intended recipient surface and approved access____________
Smallest authorized correction and decision owner____________
One controlled recheck: actual result____________
Escalation owner and next question____________

Work from the last confirmed receipt to the first unconfirmed one. If Results contains a submission, preserve that reference before editing the form. If the owner sees a file, keep its controlled reference while checking downstream access. Do not repeatedly resubmit or remap questions before reconciling the original record.

Three fictional checks, not executed

Proposed cases with actual results left blank
Synthetic caseProposed next checkActual result
DEMO-WF-01: resumed pressure-washing estimateA selected photo is missing after resume in this fictional case. Draft behavior is a hypothesis. Reconcile draft versus submitted state before asking for attachment selection again.____________
DEMO-WF-02: Site photos board column addedThe question is absent or associated elsewhere. Inspect the question-to-column relationship; do not promise remapping will recover previous files.____________
DEMO-WF-03: office sees image, technician does notInspect whether the technician uses a shared board view. Separate that recipient surface from the original upload and use an approved handoff.____________

Keep the customer update honest

The following original draft is unsent. Use it only when the submission and attached photo are known:

We are checking the photo attached to your request and where it appears in our system. Please do not submit another copy yet. We will confirm whether we need anything else by [time].

If submission is unknown, replace the first sentence with: We are checking whether your request was recorded. Give a real next-update time and an owner rather than implying receipt you have not established.

For support, privately assemble the time, role category, form surface, redacted exact error, question and column names, and first missing stage. State what is known and what remains unresolved. Use the monday review for fit, the controlled monday evaluation for broader checks, and the quote-request form comparison if choosing a different intake tool is actually the decision.

Sources and evidence

Official documentation reviewed through the verified research handoff on 7 October 2026. Source links above identify the claims they support. The records, messages and cases are original editorial suggestions.

Editorial record

Who reviewed this page and what happens next.

Commercial relationships cannot change the evidence state, fit statement, caveats, or conclusion.

Research and review
Andre Ribeiro
Published
Last material review
Next scheduled review
Evidence scope
Official monday documentation reviewed on 7 October 2026 through verified research. Original incident worksheet, diagnostic sequence, customer draft and fictional checks.
Evidence state
Documentation-based troubleshooting only. No live account, upload, permission edit, message delivery or successful recovery was tested. Actual check results remain blank.