Skip to main content
Private file storage is available as a premium add-on for our Launch plans, or included with Scale or HIPAA compliance. All files stored as private files are only accessible through on-demand time sensitive URL generation. This means that all files in your Private Storage are inaccessible until you generate a new URL in your function stack. To work with private file storage, there are two key components to understand: private file database fields and the Private File: Sign URL function.

​
Private File Database Field

To store files in your private files library and have them accessible from your function stacks, you’ll need to use a database field that is enabled for private file storage. You can enable this for any of the current file field types. Keep in mind that the file access is defined per field, which means that you can not store both public and private files in the same field.
When private files are enabled for a file storage field, a lock icon is displayed in the field name. You will also notice that private files do not display previews from the database view; this is by design, as the files are not accessible until a new URL is generated.

​
Private File: Sign URL function

To generate a signed URL that enables a private file to be accessible, you first need to retrieve the path of the file, which is stored in the database record. In this example, we have queried our files table and this is the expected return for a private image. The main difference here is that on public files, a URL is returned. For private files, no URL is provided.
We can then leverage the Private File: Sign URL function to generate a publicly accessible link to the file. Provide the path as offered from the database record, a TTL (how long in seconds the link should be valid for), and finally a return variable to contain the output of the function
When we run this function, we are returned our new signed URL.
⌘I