Skip to content

Improve registration and verification flow #13038

@NilHomedes

Description

@NilHomedes

Is your proposal related to a problem?
Participants can register but are not immediately prompted for verification, which may delay full participation and access to certain features.

Describe the solution you'd like
Modify the modal that currently appears when trying to perform an action with verification permissions. The idea is that it should be a modal explaining all the steps that must be completed in order to perform the action (1. Register, 2. Verify against the register, 3. Verification with SMS, etc.). When the participant has completed one of these steps, it should be marked as completed. This functionality should make the completion of each of these steps (register or verify) redirect you back to the modal. In this way, the participant can see how many steps they have completed and what they have left to do in a quick and simple way.

Mockups
TBD

Additional context
N/A

Acceptance criteria

  • Given a visitant
    When wants to make an action restricted by verification,
    Then the CTA of that action should say "Verify your account to {action}"
  • Given a visitant who wants to make an action restricted by verification,
    When clicks on the CTA
    Then is prompted with the Log-in/Sign-up modal
  • Given a visitant who wants to make an action restricted by verification,
    When completes the sign-up form and confirms the email,
    Then is immediately redirected to the funnel verification page,
    And can see the verifications required for that action
    So they can clearly see which verifications are still needed in order to participate.
  • The funnel should show a message saying "You are almost ready to {action} in the {component_type} {resource_tittle}"
  • Given a participant who have completed the registration process
    When leaves the verification funnel without completing the verification process
    Then a callout is shown remaindering that they must finish the verification process in order to do that action.
  • Given a participant who have completed the registration process
    When completes one verification,
    Then is redirected again to the funnel and can see the verification completed and the missing one.
  • Given a participant who have completed all the verifications enabled for an action
    When completes all the verifications enabled for that action
    Then is redirected to the original page and a successful callout is shown
    And they gain access to features requiring verified status.
  • Given an already registered participant who wants to make an action with more than one verification enabled
    When clicks on the CTA
    Then is redirected to the funnel verification page.
  • Given an already registered participant
    When click on the CTA of one action restricted only by ONE authorization,
    Then is redirected to the verification form.

Metadata

Metadata

Type

No type

Projects

Status

Merged

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions