Page Comparison

Data integrity of files in the package cannot be verified. Some or all of the files in the package are inaccessible. This most likely indicates problem with the datastore.

Corrupted data integrity. At least one file in the package is corrupted (SHA256 data checksum from last check differs from the original checksum when uploaded).

Mismatch between package encryption status and the current setting in Settings - Configuration - Data encryption - Encrypt new packages. The package is either encrypted or not, but the setting is the other way around.

Contents of some file(s) in the package matches the configured DLP filter.

Contents of some file(s) in the package is encrypted and so the file(s) cannot be checked. It can therefore be a potential threat. For details see settings concerning encrypted content detection.

Some file in the package is too large to be checked by at least one detection engine. For more see detection settings.

The package is public. Public package can be downloaded by anyone who has the link, even when not logged in. If this flag is not shown, the package is either private or internal. For details see Send a package as a logged-in user.

The package is password protected. To access it, the user must enter the correct password, otherwise the access is denied. Administrator can access the package regardless of the password, if he has the appropriate administrator’s permission, see Administrator permissions.

The package was released from quarantine. The flag signifies, that the package was quarantined and that the administrator released it from the quarantine, so users can download it.

The package was created by forwarding another package.

Persistent package. This package will not automatically expire and therefore transfer to other states (deleted, archived, shredded).

Move the package and all its files to the quarantine. A package in the quarantine cannot be downloaded by users.

Change the accessibility. The administrator can change the accessibility of a package to any of available states: public, internal, private. For details about accessibility see Send a package as a logged-in user.

Set package as persistent. Cancels the automatic expiration of the package, so the package stays in this state permanently, until the administrator manually changes that.

Unset package persistence. Restores the automatic expiration of the package again, see the related action above.

Resend notification. Resends the email notifications about the package/request to its recipients.

Encrypt. Encrypts the package files (using the server key).

Decrypt. Decrypts the package files, if encrypted by the server key. Packages encrypted by user’s password cannot be decrypted, because the key is not known.

Recheck. Runs the checks by detection engines as configured in Detection settings again. Useful for example for verifying whether new anti-virus signatures find out new malware, etc. Not available for encrypted packages.

Run a package integrity check. Recalculates the SHA256 checksums of the package files and checks for data integrity corruption.

Delete. The package is moved to deleted folder (into trash). Users do not see deleted packages and cannot download them. Administrators can see deleted packages (in trash) and can restore them, if needed. See package workflow.