Shared-folder workaround
- Sender may see folder names.
- Sender may infer project structure.
- Sender may accidentally get broader access.
- Intake and collaboration get mixed together.
Collect files securely, directly into the Vault you choose.
Let clients, customers, colleagues, or anyone else submit files into a designated Vault without giving them access to anything already stored there.
Shared folders blur boundaries. Vault Intake keeps collection separate.
PhotonFile Vault Intake
- Sender gets an upload page.
- Existing Vault contents stay hidden.
- Upload link does not become team access.
- Files land inside their own isolated Vault.
For implementation details, read the Vault Intake guide and see how Vault boundaries keep intake separate.
For client intake
Request tax packets, legal documents, design assets, media files, onboarding materials, or any other file set without asking the sender to join your workspace.
For upload-now workflows
Senders can upload when they are ready. Your team can review, organize, download, or keep the files later inside their Vault.
For controlled boundaries
A dedicated Vault with Vault Intake is a hard privacy boundary that keeps inbound uploads separate from unrelated projects, folders, and stored data.
How it works
A direct path into the right Vault
Vault Intake keeps collection inside the privacy boundary you choose. Create a dedicated Vault for a client, project, team, or workflow; configure the intake controls; share the link; and receive files there without exposing any existing contents.
1. Create a dedicated Vault
Enable Vault Intake for the Vault you want to receive into, then add instructions for the sender.
2. Share an intake link
Send the public upload link to the client or partner. They get a focused upload surface, not a view into your Vault.
3. Review files in Vault
Uploaded files land in the dedicated Vault for your team to review, download, organize, or keep without mixing them with unrelated data.
Intake controls
Set the rules before files arrive
Vault Intake controls help make inbound collection predictable for both the sender and the team receiving the files.
Instructions
Tell senders what to upload, which formats to include, and what context your team needs.
Sender notes
Require a note when every upload needs a case number, project name, client reference, or short explanation.
Access codes
Add an extra shared secret before upload. If you publish a secure intake link publicly, you should strongly consider requiring an access code.
Human verification
Use verification controls to reduce automated abuse on public upload surfaces.
Auto-expiration
Keep time-sensitive intake links from staying open longer than the workflow requires.
Upload notifications
Notify the right people when new files arrive so intake does not depend on manual checking.
What senders can do
- Open the public ingress link you shared
- Read your intake instructions
- Add files and an optional or required sender note
- Submit files into the Vault you chose for intake
What senders cannot do
- Browse your Vault contents
- See unrelated projects, folders, or files
- Manage workspace settings or team access
- Turn an upload link into broader storage access
Use Relay for live handoff
When both sides are ready now and the file should move immediately, start a live Relay transfer.
Start relay transferUse Vault Intake to receive files
When someone needs to upload now and your team will review later, give them a focused intake link.
View Vault Intake pricingUse Vault as your cloud drive
Keep complete file collections in Photon Vault, divided into isolated Vaults for long-term access, sharing, versioning, and sync.
Explore VaultReady to collect files securely?
Vault Intake is included with Relay Pro, Relay Studio, and Vault Standalone. Compare the Vault options and choose the plan that fits your intake workflow.