Odoo's native Survey app captures text, choices, ratings, and dates — but the moment a respondent needs to submit a document, the workflow breaks. Recruitment candidates cannot attach a CV, event registrants cannot upload proof of payment, quality audits cannot capture a photo of a defect, and vendor onboarding forms cannot collect a certificate. Teams end up emailing files separately, pasting shared-drive links into a text question, or maintaining a parallel form outside Odoo entirely. That fragmentation loses the connection between the answer and the file, and it leaves no clean record on the survey.user_input line where the rest of the response lives.

This is where Odoo core runs out of road: the survey.question model has no question type for binary attachments, and survey.user_input.line stores answers as char, text, numeric, date, or many2one references only — there is nothing to hold a file. We build a new question type — "File Upload" — that plugs into the existing survey engine rather than bolting a separate system alongside it. On the model side we extend survey.question with configuration fields (allowed extensions, maximum size in MB, single-vs-multiple files, required flag) and add an ir.attachment-backed store so each uploaded file is a first-class Odoo attachment linked to the corresponding survey.user_input.line. The public QWeb survey template gets an OWL-rendered upload widget so respondents on the website survey can attach files inline, and validation runs on both sides: client-side for immediate feedback and server-side in the submission controller (extension allowlist, per-file and total size caps, MIME sniffing) so nothing malicious or oversized ever reaches the filestore. Access is governed through ir.model.access.csv plus record rules so only authorized users can open a respondent's attachments from the backend, and the files surface directly on the survey result and participation views.

Because everything is anchored to the standard survey data model, the rest of Odoo keeps working: attachments flow into reporting, automated actions can fire when a file-bearing response arrives (for example, create an hr.applicant or a helpdesk.ticket and carry the attachment across), and the JSON-RPC/XML-RPC API can read the uploaded files programmatically for downstream integrations. The build targets Odoo 17.0, 18.0, and 19.0, works on both Community and Enterprise (Survey is a core app in both), and respects your instance's existing filestore and attachment-storage configuration — including object storage if you already offload attachments to S3-compatible buckets.

This is a made-to-order build, not an existing download. After a short scoping call we confirm exactly which survey types need uploads, the file-type and size policy, retention and access rules, and any automated action that should follow a submission — then we develop, test on a staging copy of your database, and install it on your instance. Typical delivery is 2-4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company deployment, tighter validation/virus-scanning requirements, object-storage integration, and automated post-submission workflows (auto-creating applicants, tickets, or documents from uploads) increase the quoted scope.