PRODUCT DOCS
Uploads, private downloads and canonical documents
Understand file scope, processing states, versions and recovery before repeating an upload or sharing a link.
Four different file contexts
A property document is owner-private evidence. An application attachment belongs to the applicant/intake review audience. A case/report/lease attachment follows its participant and workflow audience. Public listing media is deliberately selected for public presentation. Moving between these contexts is not implicit; check the audience before attaching a file.
Common processing states
A preview or progress bar is not proof of a committed document.
| Observed state | Meaning | Recovery |
|---|---|---|
| Selected file | A local file was chosen. | Review type, size and privacy before uploading. |
| Upload/processing in progress | The operation is not confirmed complete. | Keep the page open or use its supported recovery. |
| Saved row / committed evidence | The workflow returned a stored record. | Reopen it and check the intended file/version. |
| Processing unavailable | The current runtime cannot perform that operation. | Preserve the draft and use its displayed alternative; do not weaken the document checks. |
| Download expired or denied | The link/session/access context is no longer sufficient. | Reopen the authorised record to request a fresh download. |
Formats and versions
Use the types and size limits displayed by the particular uploader; they differ by workflow. Applications support PDF, JPG, PNG and WebP within the baseline 15 MB limit. A file extension alone does not establish valid content. Lease/report generation can depend on the approved document-processing runtime. Canonical signed documents are protected evidence; editing an index label or current profile does not rewrite them.
Private links and evidence handling
Secure downloads can require current session/record access and a fresh temporary link. Keep private links, resume tokens and invitation codes out of Help search, screenshots and public contact text. A public article may explain the steps, but it never receives or indexes account files. Use fictional/redacted examples for display support.
Recovering a partial operation
After a failed upload or unknown save outcome, reopen the existing index/task and look for the row before sending the file again. Confirm the correct record and version before signing or downloading. If a file is wrong, use the offered removal/correction/successor path and preserve signed history. Do not treat a browser preview or successful HTTP response as proof of valid legal service or document suitability.
Product guidance, not legal advice or a guarantee of compliance. For jurisdiction-specific requirements, check current official guidance or obtain advice for your circumstances.