The permissions of saved files are inherited from the directory on the server where FileUp initially caches each uploaded file.

Please choose from the following three scenarios to determine where FileUp is caching the upload:

1. You are using FileUp's ISAPI filter. In most cases, the ISAPI filter is only necessary when using FileUp version 4 in ASP.NET

There is a registry key located at:
HKEY_LOCAL_MACHINE\SOFTWARE\Software Artisans\SA-FileUp\IsapiTempDir

This key should point to a folder where you would like to temporarily cache the upload and inherit permissions from.

2. You are using the HTTPModule in version 5.x of FileUp

There is a registry key located at:
HKEY_LOCAL_MACHINE\SOFTWARE\Software Artisans\SA-FileUp\Parameters\FileUpTempDir

This key should point to a folder where you would like to temporarily cache the upload and inherit permission from.

3. You are using FileUp WITHOUT the ISAPI filter or HTTPModule

The cache location is set via the Path property of the FileUp object.

When the Path is not specified, FileUp will use the %TEMP% Environment variable on the server. By default this is
%WINDIR%\Temp.

Note that the Path should be set immediately after instantiating the FileUp object.

<%
set upl = Server.CreateObject("SoftArtisans.FileUp")
upl.Path = "C:\uploads"
%>

The permissions of the uploaded file will now inherit from the "C:\uploads" directory.

Please see Windows 2003 and IIS 6 support for version 4.x of FileUp to find out more about your options for using FileUp 4.x with IIS 6.

A simple way to make sure the permissions of the file are the same as the upload directory is to configure your application to cache the files in the same directory where you will ultimately save them. If that is not possible, you can change file permissions after the upload is complete using FileManager, which comes bundled with FileUp.