Signup abandonment
External recipients may stop at account creation, especially for a one-time delivery or a time-sensitive review.
How to share files without requiring an account
Use a PhotonFile Relay link when the recipient is ready now, or a scoped Vault share when they need to download later. Recipients can use either one without creating a PhotonFile account.
Account-free delivery should still be controlled. Share the smallest useful scope, verify who receives the link, and end access when the job is complete.
Live Relay: Both you and your recipients must remain online until the transfer completes. Keep your browser tab or desktop app running until all downloads finish.
Cloud Transfer: Recipients can begin downloading while you upload. Keep your browser tab or desktop app running until your upload finishes. After that, you can close it or go offline, and recipients can still download your files using the shared link. Cloud Transfer allows one confirmed delivery. Once the complete transfer is confirmed saved, new downloads stop and automatic deletion begins. Use Vault for repeated downloads.
Cloud transfers default to seven days from upload completion. Choose one to seven days with Free or File Pass funding, or up to the server maximum with Relay subscription funding. Use Photon Vault to keep, share, and sync files over time.
A link to stored files is not workspace membership.
The recipient should receive the file, not a new seat, a team invitation, or browse access to unrelated content. Relay and Vault shares keep the external task separate from internal workspace access.
Why forced account creation adds friction
A recipient who only needs one file should not have to choose a password, verify a new account, learn a workspace, or become a long-term member. The delivery path should match the task.
Unnecessary workspace access
A folder invitation can reveal filenames, collaborators, or unrelated material beyond the intended deliverable.
Seat and offboarding overhead
Turning every client or contractor into a member creates lifecycle work that the file delivery did not require.
Unclear link ownership
Recipients do not need an account, but the link should still be tightly scoped and expire when the work is done. A forwarded link is still a link someone else can use.
Compare low-friction delivery methods
Choose based on whether the recipient should receive now or later. Both PhotonFile paths avoid requiring normal workspace membership, but they create different access windows.
| Method | When it works | Limitation | How PhotonFile fits |
|---|---|---|---|
| PhotonFile Vault share | The recipient needs later access to a selected file or folder | The retained content uses Vault capacity and the share must be reviewed | Creates scoped access without normal Vault membership and can be revoked or limited |
| PhotonFile Relay | Both sides are ready for a live handoff | The session is active only while the transfer is running | Lets the recipient receive through the link without creating a PhotonFile account |
| Email attachment | The file is small and low risk | Size limits, forwarding, and mailbox copies are hard to control | Use the email for context and send a PhotonFile link for the actual file |
| Cloud-drive guest link | The organization already manages external links carefully | Folder scope and inherited permissions may expose more than intended | Use a Vault share to target the selected item inside a distinct Vault boundary |
| Guest workspace account | The person needs repeated collaboration and internal access | Provisioning and offboarding are excessive for a one-time download | Use account-free delivery for the file and reserve membership for ongoing work |
| Messaging platform upload | A small, routine file in an existing conversation | Retention, forwarding, and file handling may not fit sensitive work | Keep the conversation for context while PhotonFile handles the file path |
Decide the access window before sending
-
1. Choose now or later
Use Photon Transfer for Live + Cloud delivery. Cloud permits temporary pickup after upload when the sender is offline. Use Vault for ongoing access and managed sharing.
-
2. Select the smallest useful scope
Share one file for one deliverable or one carefully reviewed folder for a complete package.
-
3. Verify the recipient
Confirm the address, conversation, or other trusted contact path before sending the link.
-
4. Choose link controls
For Vault shares, use the current expiration, usage-limit, and revocation options that fit the delivery.
-
5. Explain the delivery
Include the filename, purpose, approximate size, deadline, and any checksum or handling instructions.
-
6. Close access deliberately
Revoke the Vault share when it is no longer needed and remember that downloaded copies remain with the recipient.
Vault share
Let the recipient download later without joining the workspace
- 1. Upload the completed file or folder. Use the Vault that matches the client, project, or sensitivity boundary.
- 2. Wait for upload completion. Confirm every intended item appears before creating the share.
- 3. Select the exact resource. Do not share a higher-level folder merely because it is convenient.
- 4. Create the share link. Review the current expiration and usage-limit options before copying it.
- 5. Send the link through a trusted channel. The recipient can use the documented share-download flow without creating a PhotonFile account.
- 6. Review and revoke. End the share when the delivery is complete or the recipient should no longer have access.
Relay
Complete a live handoff without recipient signup
- 1. Confirm the recipient is ready. Live Relay is not a link to stored files.
- 2. Select the file or files. Check the version and size before beginning the transfer.
- 3. Choose optional client-side encryption. Use it in supported flows when the recipient environment can open the full link.
- 4. Start the transfer and share the live link. The recipient can receive the Relay transfer without creating a PhotonFile account.
- 5. Keep both sides active until completion. Use eligible resume or Retry behavior after an interruption.
- 6. Verify receipt. Have the recipient confirm the expected file, size, and checksum when required.
No recipient signup
The external task stays small
The person opens the link and receives the intended file without becoming a workspace member.
Scoped access
A Vault share targets one resource
The link does not automatically grant access to the full Vault or the team workspace.
Different timing
Live Relay, Cloud transfer, or Vault
Do not use a live Relay link when the recipient expects an attachment-style download window.
Treat the full link as a credential
Account-free access shifts the control from a login to the link and its share settings. Send it only to the intended recipient and avoid posting it in broad or permanent channels.
Anyone with the usable link may be able to access the file while it remains valid.
Revocation cannot erase a completed download
Stopping a Vault share prevents future use of that link, but it does not remove copies that the recipient already downloaded, forwarded, backed up, or printed.
Choose the recipient and scope before sending, not only after.
Use membership only when the relationship needs it.
A client, reviewer, or contractor who needs repeated access to a shared work domain may eventually need a team or Vault access workflow. For a one-off download, a scoped link is usually enough.
Common questions
Frequently asked questions
Does the recipient need a PhotonFile account?
No. Recipients can download from a Vault share or receive a Relay transfer without creating a PhotonFile account.
Should I use Relay or a Vault share?
Use Live Relay when both you and your recipients can remain online until the transfer completes. Keep your browser tab or desktop app running until all downloads finish. With Cloud Transfer, recipients can begin downloading while you upload. Keep your browser tab or desktop app running until your upload finishes. After that, you can close it or go offline, and recipients can still download your files using the shared link. Use a Vault share for files or folders you want to keep and share over time. Cloud Transfer allows one confirmed delivery. Once the complete transfer is confirmed saved, new downloads stop and automatic deletion begins. Use Vault for repeated downloads.
Does an account-free link expose my whole Vault?
No. A Vault share is scoped to the selected file or folder. It does not grant normal Vault membership or broad workspace access.
Can I revoke a Vault share link?
Yes. Revoke the share when access should end. A file already downloaded may still exist on the recipient device, so revocation is not remote deletion.
Can a share be limited to one download?
Vault sharing supports usage limits, including a one-completed-download workflow when configured. Confirm the current option in the share dialog before relying on it.
What happens if someone forwards the link?
Treat the full link as access. Anyone who receives it may be able to use it while the share or Relay session remains valid, so verify the recipient and use expiration, usage limits, or revocation where appropriate.
Keep going
Related guides
Send sensitive documents securely
Add recipient verification, deliberate retention, and controlled access to the delivery.
Securely deliver client work
Package a finished release and hand it off without opening the project workspace.
Send encrypted files without a cloud-drive folder
Use a live Relay path when the file should not remain in storage.
Product and technical references: Vault sharing guide Relay guide Vault overview Vault technical security Relay technology
Give them the file, not a new account.
Choose Live + Cloud delivery for a temporary handoff, or a scoped Vault share for ongoing access. Close the access window when the job is done.