Skip to content

Web Client Updates, Patches, and Release Notes

05/14/2025


LeapFILE Web Client build v2.2.1 is now deployed:
  • Require email verification for dropsite Secure Upload
  • Incoming transfer blocking rules
New:
  • Require one-time email verification for Dropsite Secure Upload.
    • Dropsite visitors will no longer be able to send Secure Upload transfers anonymously without verifying their email address.
    • In order to send a Secure Upload transfer, they will need to enter their name and email, after which a 6-digit verification code will be sent to their email inbox for them to use to verify ownership of the email account.
    • Once their email address is confirmed, they will be able to proceed with Secure Upload as normal.
  • Allow admins to configure blocking rules and exception patterns on incoming transfers.
    • An admin can go to the new Account --> Incoming Transfer Rules page to create, edit, or remove blocking rules and exceptions.
    • A rule tester is also provided for convenience to quickly test your rule and exception patterns against a specific email address of interest.
How do Incoming Transfer Blocking Rules work? When Dropsite users go to Secure Upload and verify their email, blocking rules are applied against their email address before they can make a transfer. If a user matches a blocking rule pattern and does not match with any exception pattern, they will be denied from sending a Secure Upload transfer. If a user is denied and they think this is in error, they will have the option of clicking to request access which will send an email to your LeapFILE account's official administrator.

*NOTE: if an account is set up for Guest User sign-in as a requirement for Dropsite Secure Upload, the incoming transfer blocking rules are instead applied upon a visitor clicking on "Guest User Registration" to create a new guest user. Incoming transfer rules are NOT checked on sending transfers in this configuration. Rules are checked only upon trying to register a new guest account. This means that any existing, previously approved guest users can continue to send Secure Upload transfers even if their emails happen to match an existing block rule at the time of sending a transfer.

Feedback and Knowledge Base