Practical guide

Choose a request, delivery link or collaborative folder

Last materially reviewed 2026-09-29

Quick answerChoose by the other person’s required action: send material in, retrieve a release, or work on shared files over time.
What to know

Name the direction

If the client only needs to provide material, begin with an intake route. If the client only needs the completed package, begin with a delivery route. If both parties must alter a shared working set, investigate collaboration. Do not start from the most powerful permission available and then try to explain why the client will not use it.

What to know

Separate access from convenience

An account-free route can reduce friction but does not establish the identity of every person who receives a forwarded link. An account-required route can be appropriate for sustained work but may add onboarding effort. Make that trade-off explicit. A convenient URL is not automatically the right mechanism for sensitive material or an organization with required identity controls.

What to know

Match the documented mechanism

pCloud’s file requests, shared links and folder invitations are different features. The first two can support account-free exchange in their documented roles; collaboration requires a pCloud account and has region constraints. Check your exact task against current documentation. Avoid treating an upload-enabled shared link as identical to a dedicated file request because the recipient requirements can differ.

What to know

A fictional route choice

A print designer needs the client’s approved logo, then later delivers print-ready exports. A request can handle the inbound file and a separate release link can handle delivery. The client does not need to manage the studio’s working folder. If an outside designer joins the production work, that is a separate collaboration decision with its own permissions and end date.

What to know

Put the decision into practice

Before sending, complete this sentence: the recipient needs to do this action, with this material, until this point. Then identify the smallest supported route that meets it. If the sentence contains both submitting inputs and approving outputs, split it into separate tasks instead of granting broad collaboration by default.

Continue when useful

Next: Request vs upload link

Check the recipient’s account requirement and visibility for the exact collection mechanism before sending instructions.

Open Request vs upload link →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. pCloud file requests — Merchant documentation · help.pcloud.com · Merchant-controlled · checked 2026-09-29
  2. pCloud shared links — Merchant documentation · help.pcloud.com · Merchant-controlled · checked 2026-09-29
  3. pCloud folder invitations — Merchant documentation · help.pcloud.com · Merchant-controlled · checked 2026-09-29
MATCH THE ROUTE TO THE TASK

What does the other person need to do?

Required actionStart by evaluatingDo not assume
Send materials inA bounded file requestEvery upload mechanism is account-free
Retrieve final filesAn identified release linkA preview means a usable original
Edit togetherSupported folder collaborationEvery account region and role is compatible
Confirm completionThe agreed project processDownload activity equals acceptance