Create a client file upload request

Create a client upload request, choose its destination and limits, test the public page, and verify each received file in your workspace.

Last reviewed

A file request lets a client upload into a destination you control without joining your Dosya workspace. In File requests, select New request, choose By link or By email, set the acceptance rules, then test the recipient page before using it for important delivery.

A sharing link sends files outward. Use Create a sharing link when the files already exist in your workspace and recipients need to open them.

Before you start

  • Select the workspace that should own the received files. Creating a request requires upload files permission because its URL delegates that permission to someone outside the workspace.
  • Choose a live, visible destination inside your allowed folder subtree. A configured Full lock on that folder or an ancestor blocks public uploads even when you personally unlocked it for an hour.
  • Check the owning account’s remaining plan storage and any workspace total-storage cap. File requests have no separate storage pool: accepted bytes consume that workspace’s ordinary allocation.
  • Decide whether the request should use a public bearer URL or emailed invitations. By link needs no account. By email records and sends invitations to up to 100 valid addresses in one request.
  • Prepare a harmless sample. A successful test uses storage and one Max files slot. Leave room for both the test and the client’s delivery; an ordinary owner-side file deletion does not return the request slot.

Steps

Build the request

  1. Open File requests and select New request. On an empty page, Create a request opens the same Request files dialog.
  2. Select the Request files tab that matches this client handoff:
    • By link creates one URL for you to copy and distribute.
    • By email requires at least one Email addresses entry and sends an invitation. Split a list larger than 100 across requests.
  3. Enter Title (optional) and Message (optional) with the exact documents, naming rules and deadline. Do not include account credentials.
  4. Add Password (opt) when the URL needs a shared secret. The trimmed password must contain at least eight characters.
  5. Set Expires to Never, 1 day, 7 days, 30 days or 90 days. The form starts at 7 days. Expiry closes new uploads; it does not delete received files.
  6. Select Upload destination. Root (workspace top level) means the workspace root for an unrestricted member and the member’s assigned anchor for a folder-confined role.
  7. Review Put each uploader in their own folder. It is on by default:
    • With a title, Dosya first creates a new title-named folder in the selected destination, using a suffix such as “(2)” if necessary.
    • Each browser then receives its own child folder, named from the entered name, the invited address associated with that recipient URL, typed email, dropped folder name or a six-character guest reference in that order.
    • Turning the option off places submitted paths directly in the selected destination. This setting is fixed at creation in the current web editor; create a new request if the organization model must change.
  8. Expand Advanced options when the delivery needs narrower rules:
    • Allowed extensions accepts a comma-separated list such as .pdf, .docx, .jpg. The browser rejects missing or disallowed filename extensions. This checks the name, not the file’s contents.
    • Max file size (MB) caps each file, not the whole submission.
    • Max files counts accepted files across every uploader. Concurrent attempts reserve slots atomically so the cap cannot be exceeded by two clients racing for the final place.
  9. For By link, select Generate link, save the URL under Request link, then select Done. For By email, choose Send request and wait for Request sent.
Request files dialog for creating a client upload URL, with By link, Root workspace destination and Generate link identified.
Choose By link, confirm where client files will land, and review the request rules before selecting Generate link. Open full-size screenshot.
Created client file request showing its Request link, Copy control and Done button.
Save the complete request URL with Copy; Done closes the result after the address is safely recorded. Open full-size screenshot.

Test the public upload page

  1. Paste the generated client-upload address into a private browser window, then match its workspace identity, title, message, deadline and remaining file slots to the owner form.
  2. If the page asks for a password, enter the request password and select Unlock. This creates a request-specific access grant for 30 minutes; it is unrelated to a Dosya account password.
  3. Before adding files, optionally enter Your name (optional) and, when shown, Your email (optional). These labels help organize deliveries; typed values do not verify the sender’s identity.
  4. Check the intended sample’s name, contents and size on your device. Use Browse files, Choose a folder or Drop files here. Touch devices can instead show Photo library, Take a photo and Browse files. Adding, dropping or pasting accepted files starts uploading automatically; there is no separate Upload button.
  5. Watch This transfer. Active rows show transferred bytes and percentage; rejected rows show the reason. A waiting or rejected row has Remove, while an active transfer has Cancel. Sending may already have started, so cancellation does not prove that no file reached the server.
  6. Keep the page open until the green receipt says the requester has this file or has these N files. It records the received size, local date and time, and request reference. A filename in the queue or a progress percentage alone is not delivery confirmation.
  7. If a password grant expires during a long transfer, enter it again under Your access timed out and choose Unlock and continue. For other failures, read the row’s message and follow the uploader guide before retrying. If the result is uncertain, check previous submissions and the owner’s destination before adding the same file again.
Example file-request receipt naming the requester, received size, time and reference, with a separate rejected file above it.
The green receipt confirms the accepted delivery. A rejected row can remain above it, so check which files succeeded before telling the client the whole batch is complete. Open full-size screenshot.

Confirm what you received

  1. Return to File requests and open the request detail. Reload an already-open tab.
  2. Match the client’s intended filenames and sizes to the received rows. Use the receipt’s total size, time and request reference to identify the delivery; the stamp does not list each filename.
  3. Open Files and inspect the configured destination. When uploader folders are enabled, follow the title folder and uploader folder rather than expecting the file directly at the selected level.
  4. Tell the client the delivery is accepted only after both sides agree on the received item. Returning submissions are associated with the visitor’s browser cookie or recipient-specific invitation link; neither makes a typed name proof of identity.
Owner request detail listing the completed client-example.txt upload with size and submission information.
The owner confirms a completed client delivery from the request’s uploaded-file table, then checks the same file in its destination folder. Open full-size screenshot.

Expected result

The client sees the stamped receipt, the owner sees the same filename and byte size on the request detail, and the file exists under the chosen destination structure. The upload consumes ordinary workspace storage without making the client a workspace member.

Limits and exact refusals

Request-specific acceptance rules and the owner plan/workspace storage gates both apply; the stricter result wins.

ConditionBrowser or upload response
Request was closedThis request was closed
Deadline passedThis request has expired
Count is exhaustedThis request has reached its file limit.
Request size rule failsFile is too large. Maximum size is N.N MB
Extension is refusedThe browser says .ext is not accepted here - send …; an upload-time refusal can say File type .ext is not allowed. Accepted: …
Extension is missing while a filter is setThis file has no extension, so its type cannot be checked
Destination later receives Full lockThis upload request can no longer accept files.
Workspace storage is exhaustedA storage-quota refusal; the owner must free capacity or change the plan

The browser checks files before starting, and the server rechecks live rules during upload. Another client can use a remaining slot or storage capacity after this page loaded.

Blank request fields mean no request-specific extension, per-file-size or file-count ceiling. The owning account’s storage entitlement and the workspace total-storage cap can still refuse incoming bytes. Never removes only the request deadline; it does not create extra storage.

Manage or end collection

The detail page provides Copy link, Edit, Recipients, the received-file table and Revoke while active. Editing future rules does not revalidate completed uploads. Moving the destination does not relocate earlier submissions.

Revocation is irreversible and stops future single-part and multipart calls. It notifies recorded recipients, but it leaves their completed workspace files and the owner ledger intact. Use Edit or close a file request before deleting any retained material.

Troubleshooting

The request cannot be created in a folder. Confirm the folder exists, is inside your assigned subtree and is visible to your role. A hidden destination looks missing. A configured Full lock returns folder_locked; a personal unlock grant is intentionally ignored because the public URL outlives that grant.

An invitation did not arrive. The request can exist even when delivery fails after creation. Copy its URL from File requests, verify the address, and use the recipient controls to resend without creating a duplicate inbox.

The sender sees a filename but no receipt. Accepted files start automatically. Ask them to keep the page open and read the row’s progress or rejection message. A filename under This transfer alone is not confirmation. If the connection ended ambiguously, check the request detail and destination before they retry to avoid sending a duplicate.

The client sees a storage refusal. Only a workspace member can free capacity, raise the workspace cap or change the owning plan. The outside uploader cannot solve it by signing in or choosing a different browser.

A large upload stopped after revocation, expiry or a new destination lock. Those gates are checked throughout multipart transfer. Reopen collection with an edited future expiry when appropriate, or create a new request after resolving the configured lock. A revoked token itself cannot return.

Frequently asked questions

Does a client need a Dosya account?

No. The public request URL authorizes the upload subject to its password, deadline, destination and file rules.

Is a file request private because it was emailed?

An invitation can identify a recorded recipient, but anyone holding a plain request URL may still reach the public page unless its password protects it. Share sensitive request addresses carefully.

Can uploaders remove a submitted file?

The public page can show Remove to the same visitor while the request remains usable. Confirming it permanently purges the received file, its versions, its share records and the stored objects they reference. This withdrawal bypasses Deleted, so neither the uploader nor the owner can recover it from Dosya Trash. An ordinary owner-side Delete in Files is different: that soft-deleted item appears under Deleted and follows workspace retention until it is purged.

Was this helpful?

Loading helpfulness results…

Voting saves a necessary ballot cookie for up to 180 days so you can change your answer.

Questions and replies

Ask about the steps in this guide. Questions are reviewed before publication.

Keep account details, credentials and private files out of public questions. Use private support for those.

Loading questions…

    Sign in to your Dosya account to ask a question.

    Check the outcome before you retry

    Use these shared checks when a task needs a second look.