Tamper Detection & Notifications

Tamper detection

With Enable Tamper Detection on in Settings, Frappe Sign can check whether a stored file still matches the hash it recorded when the file was generated - covering the Source PDF, Signed PDF, Audit Certificate, and Final Verification PDF, on both Frappe Sign Request and Frappe Sign Certificate records.

Tamper status is one of:

Not Checked
Passed
Failed

A status change is recorded as an activity comment. If a check flips to Failed, the creator of the affected signing request gets an email notification - this is the one thing in Frappe Sign that proactively alerts a human, rather than waiting to be asked.

Manual checks

Both Frappe Sign Request and Frappe Sign Certificate have a Verify Tamper Status action - it ignores submitted/locked state and updates tamper status on demand, useful for spot-checking a specific document right now rather than waiting for the schedule.

Scheduled checks

If you want this running automatically, wire up the scheduler in hooks.py:

scheduler_events = {
    "daily": [
        "frappe_sign.utils.notifications.send_daily_signing_reminders",
        "frappe_sign.utils.tamper.run_scheduled_tamper_checks",
    ],
}

Notifications

• Completion notifications - sent to the creator and signers once a request completes. If a final verification package exists it's attached; otherwise the signed PDF and audit certificate are sent separately.
• Reminder notifications - a daily reminder can go out to whichever signers are currently eligible to sign (respecting Default Reminder Days in Settings) - for sequential signing, that means only the current order/cohort, never someone who hasn't been unlocked yet.

This is the last page of the walkthrough - back to Overview & Legal Notice for the full picture, or jump straight back into your own Frappe Sign Settings to start configuring for real.