Sending a package in FileRunner is as straightforward as composing an email. To begin, navigate to the ‘Share’ tab in FileRunner (formerly known as 'Create Packages,' in previous versions), as illustrated above.
Create your Package
Now, let's ensure your package includes essential details. Each package must have a unique name and at least one recipient. You can also add a personalised touch with an optional message.
Recipient Types in FileRunner
Verified User
These users have a FileRunner account and can seamlessly send and receive packages. Add them to your package from the recipients list, as demonstrated below.
Click the input area and either select from the scrollable list of saved recipients or type to filter the results
Unverified User
No FileRunner account? No problem! Unverified users can receive packages using just their email address. Keep in mind; they can't send packages themselves. To include an unverified user as a recipient, simply click the “+” button and enter their email address as prompted. You can easily locate this user in the 'Unverified User' section of the recipients list for all your future package-sending needs.
How to add a user without a FileRunner account (an unverified user) to a package
Depending on your Project settings, sending packages to unverified users may be restricted for security reasons. If you're the Project Administrator and want to enable this feature, refer to our guide on Managing Your Project for step-by-step instructions.
PIN Verification
PIN Verification is a security feature akin to two-factor authentication. To unlock a package of this type, PIN verified packages require the entry of a 6-digit code that is sent to the user's mobile phone via SMS text. This feature can be enabled for all users or unverified users only.
Enabling PIN verification
To activate PIN verification for a package, switch on the feature using the toggle button as demonstrated and choose whether it applies to all or only unverified users.
Checking Recipients' Mobile Numbers
After adding users to the Recipient list, check if they have a saved mobile number for PIN verification. A green check next to their email indicates this is the case. Clicking the number allows editing. If a number is missing, use the 'add' button to include it before sending.
Editing Mobile Numbers for Verified Users
Editing a verified user's number is possible for the specific package only, serving as an override. Only the numbers added at the time of sharing a package can be used to unlock it - this is essential for maintaining the package security . Updating a user's phone number in their profile after sending the package will only apply to subsequent packages. Contact our support team to update a user's number for PIN verification post-package delivery.
Again, dependent on your Project settings, PIN verification may be enforced for all packages on your Project. If this is the case you will not be able to turn off PIN verification. However, if it is only enforced for unverified users you can decide to additionally add it to verified package recipients. If you are a Project Admin and want to know more about how to enforce this feature see Managing your Project.
Access Period
By default, packages are accessible to recipients immediately after upload and for a 10-day duration. However, files are stored for a total of 15 days and users have the flexibility to customize the access period within this 15-day window.
To set a specific access period different from the default, click the calendar button. Choose the desired start and end times and dates for the package.
Recipients will not be notified about the package until the access period begins. This feature is particularly useful for handling embargoed content or managing your workflow. For instance, you can complete your upload at a convenient time and delay discussions with end clients or colleagues until a later date.
In the event, that users do not download the package within their allotted time, senders have the option to enable a 3-day extension. This extension can be activated within the last 24 hours before the package expires. Please note that this extension feature is a global setting for your project and is currently managed within our Internal management tools. If you don't have access to this feature but would like to, please contact our support team for assistance.
Attaching files to your Package
After specifying the package name, recipients, and an optional message, it's time to add files to your package. You can select individual files or entire folders using the buttons located at the top right of the package file list. If selecting a folder, your file directory structure will be maintained upon package delivery.
Package size limits
FileRunner packages have no limits on the number of files or overall package size (Bytes). Users commonly send packages as large as one terabyte. However, depending on your connectivity during upload, consider splitting very large packages into 150GB-250GB sizes to minimize the risk of interruptions. This is not essential but may be practical.
Uploading your package
Once your package is ready, click the red 'Send Package' button in the top right corner. Ensure you have followed the steps correctly— you need a package name, at least one recipient, and one attached file. For PIN verification, ensure all users have a phone number added. The button will be disabled until this is fully complete.
When your upload starts the upload drawer will open on the right-hand side of the screen. It may take a moment for the upload to get going. Once in progress, you’ll get an update on the overall percentage of progress, an estimated time remaining based on the average speed of upload and overall package size, the current speed, number of files uploaded and the number of bytes uploaded. The speed can fluctuate a bit and is most accurate in the middle of the upload as there is a little overhead in our processing at both the beginning and end of the upload.
You will have options to both Cancel and Pause the upload. Cancelling aborts the upload process entirely whereas pausing will temporarily pause your upload. Note this will pause the progress of your entire queue should you have more than one package waiting to upload. Pausing can be resumed so long as the browser session is not ended. This is therefore only for use when you intentionally need to pause the connection for example if you are moving networks or you need to free up bandwidth for another use case.
During the upload, you may minimise the upload drawer at any time allowing you to queue up further packages for upload or review other pages in the site. The minimised bar will remain at the right side of the screen with a smaller version of the progress bar. Clicking the minimised bar will reopen it. If the bar changes colour at any point this is because we are warning you of either a potential issue or notifying you that the package is in an error state.
Once the upload is complete, close the upload drawer by clicking the 'x' at the top (when open) or at the bottom of the minimized bar.
After the Upload
You don't need to wait for large uploads. After your files reach FileRunner servers, a short build process finalizes the package for recipients. You'll receive an email notification when the transfer and build process is complete. Check your Sent package list if you don't receive the email immediately. If the package isn't there after a short wait, contact our support team.
If the Access period is set to start immediately following upload, recipients will also receive an email. Refer to our guides on downloading FileRunner packages for more details. If recipients don't receive emails, consult our troubleshooting guide on email notifications.