Verified

Changing Signing and Notification Methods After Publishing an Envelope

Updated

If you need to change how a recipient receives their invitation (Email vs. SMS) or switch their required signing method (e.g., from BankID to SMS or Touch Sign) after an envelope has already been published, you do not need to cancel or recreate the transaction. You can modify these settings directly from the Edit Recipient modal—provided the recipient has not already completed their signature.

👥 Who Is This Relevant For?

  • Web App Senders: Senders and administrators managing active envelopes who need to adapt to recipient technical difficulties or changing verification requirements on the fly.

  • API Integrations: Fully supported. Programmatic integrations can update pending recipient methods via the Verified API.

⚙️ How It Works

You can update both signing and notification preferences from your account dashboard:

  1. Log into your Dashboard or in the Archive and locate the active transaction.

  2. Click on the envelope entry to expand its details.

  3. Locate the recipient whose settings you need to adjust and click the Pen (Edit) icon ✏️ on their row.

  4. In the Edit Recipient modal, adjust your preferences:

    • Notification Method: Switch how the link is delivered (e.g., Email or SMS).

    • Signing Method: Select an alternative identity/signing verification method (e.g., BankID, SMS code, or Email sign).

  5. Click Save and Notify.

Once saved, the platform immediately applies the new parameters and dispatches an updated invitation to the recipient.

What happens if the recipient opens their old invitation link?

Both the original invitation link and the new one will automatically direct the recipient to the newly defined signing method. The signing session checks the current server configuration in real time, ensuring the recipient cannot bypass the updated requirement by opening an earlier message.

warning Warning.