Portainer backup restoration – missing automatic integrity verification before activation

When restoring a Portainer backup, the administrator imports an SQLite database file to recover stack definitions, user settings, and endpoint configurations. The current feature does not automatically verify that the imported file is intact or unaltered before it becomes the active database, leaving the verification step to the operator.

This raises the question of whether Portainer should enforce an integrity check (e.g., a SHA‑256 comparison) as part of the restore process, and what permission boundaries should govern any override or bypass of that check.

• Should Portainer automatically compute and compare a checksum of the backup file before activating the restored database?
• What role or permission level should be required to disable or override an automatic integrity verification?
• How should the system notify administrators when a backup fails the integrity check during restoration?