Documentation
-
Home
-
Getting Started
-
Common Tasks
-
The Servd Plugin
-
Project Settings
-
Domains & SSL
-
Importing & Cloning
-
Assets
-
How Do I Include Compiled Assets In My Bundles?
-
Can I use my own domain for assets?
-
Bulk Uploading To The Servd Asset Platform
-
Manage Assets Using Cyberduck
-
Manage Assets Using Transmit
-
Manage Assets Using FileZilla Pro
-
Manage Assets Using s3cmd
-
Manage Assets Using AWS CLI
-
What Happens If I Exceed My Assets Storage Limit?
-
Considerations for Video Files
-
Imager X Integration
-
Upgrading to Asset Platform V3
-
Use Custom Domains for Assets
-
Storing Private Files
-
Manage Assets Using rclone
-
-
Logs
-
Plans and Billing
-
Addons
-
Team & Project Management
-
Project Security
-
Your Account
-
Troubleshooting
-
Cookbook
-
Now & Next
-
The Small Print
Storing Private Files
V2 of our Asset Platform does not support fully private files. If you need to store private files and your project is using our V2 Asset Platform you can upgrade using the guide here.
By default, all files uploaded to the Servd Asset Platform are publicly downloadable, however there are situations in which you might need to store fully private files which can only be downloaded via an authenticated method within Craft.
Our method for achieving this is simple, any files stored within a directory on the Asset Plaftorm named private will be made private.
We recommend creating a separate Craft Volume for your private files, and linking this with a Servd Filesystem that has the subfolder property set to private to provide a clean separation between your public and private files.