Build a Tally file submission form: size, file types and link access

Define the files and review process

The example accepts one PDF linked to an application ID and an optional image. Specify the allowed formats, counts and practical size limit before building. For highly confidential documents, separately confirm that the chosen transfer method fits organizational handling requirements. File intake is not complete merely because a large upload succeeds; an operator still needs to identify and review the submission.

Add a file-upload block

Add the upload input and label the exact document expected. Configure minimum or maximum counts, maximum size and accepted formats where needed. Tally currently documents a free per-file limit of 10MB and Pro for larger uploads; verify current subscription terms before relying on a limit. Choose operational requirements rather than automatically accepting the largest possible file.

Link uploads to an application and submission version

Collect a stable application or case identifier instead of relying on a name. Decide whether resubmission supplements the first file or replaces the approved version, and preserve submission time and version information accordingly. Identical filenames do not establish identical contents. Keep enough information to distinguish a correction from a duplicate click or a different applicant's similarly named file.

Separate format validation from content review

A PDF-only restriction reduces input mistakes but does not establish that the document is correct, complete or safe to open. Review the case ID, necessary pages and readability before forwarding or publishing anything. Keep a review-pending state and define how the team requests a replacement for a corrupt or inappropriate file. Do not silently treat a successful upload as approval.

Inspect access to exported links

Tally warns that file URLs exported to destinations such as Google Sheets may be accessible to people with those links. Sharing the spreadsheet can therefore broaden access to submitted files. Check in-product access and externally exported links separately. Avoid posting uploaded-file links into a broad channel simply because the related request number is safe to share.

Try boundary cases in the published form

Check a small allowed file, a disallowed format, an oversized file, multiple files and a replacement submission. Reconcile the application identifier and uploaded object after the completion screen appears. Try file selection and upload on a phone as well. A rejection should tell the respondent how to fix the problem rather than leaving an unclear failure at the final step.

Assign retention and recovery responsibilities

Decide who keeps, replaces and deletes submissions and for how long. Forwarding a file elsewhere can leave copies in both systems, so identify every retained location. If an integration stops, inspect the original submission before asking the applicant to upload again. Add automation only when the required transfer or review process justifies it. This guide proposes acceptance cases without claiming executed uploads or verified security of an untested account.

• Build a Tally contact form: questions, publishing and checking submissions
• Send Tally responses to Google Sheets: native integration and reconciliation
• Choose attachment-request forms by access and retention