Skip to content

[FEATURE]: Improve UX flow for email-token signature process (clear guidance + step-by-step flow) #6962

@yharroch

Description

@yharroch

Is your feature request related to a problem? Please describe.

The current email-token signing workflow is not intuitive for external signers.

When a signer clicks the signing link, they are prompted to enter their email address again to receive a verification code, but:

  • There is no clear explanation of why this is required.
  • The user does not understand what is happening.
  • The process feels circular and confusing.
  • There is no visual indication of progress (step 1 / step 2 / step 3).
  • This creates friction and confusion, especially for non-technical users.

Describe the solution you'd like

1️⃣ Add a progress indicator
Example:

  • Step 1 of 3 – Email verification
  • Step 2 of 3 – Code validation
  • Step 3 of 3 – Signature
    This would drastically improve user confidence.

2️⃣ Add explanatory text
Users currently do not understand:

  • Why email is requested again
  • Why a code is required
  • Whether this is normal or an error
    Adding contextual explanation would reduce support requests.

3️⃣ Avoid reopening modal loops
After code validation, the interface should transition clearly to the final signature state without reopening the verification modal.


Expected behavior (Suggested UX improvement)

Proposed explicit step-by-step flow:

Step 1 – Identity verification

  • Display clear message:

To sign this document, we must verify your identity.
Enter your email address to receive a verification code.

  • Button : Send verification code”

Step 2 – Code validation

  • Display clear message:

A verification code has been sent to: [email protected]
Please enter the 6-digit code below.

  • Button : “Validate code”

Step 3 – Signature confirmation

  • Display clear message:

Your identity has been verified.
You can now sign the document.

  • Button : “Sign document”

Describe alternatives you've considered

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status

    4. to release

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions