All Collections
Understanding Application Registration Flows from the Student Perspective
Understanding Application Registration Flows from the Student Perspective

Learn about the different application registration flows for students with and without Element451 records.

Michael Stephenson avatar
Written by Michael Stephenson
Updated over a week ago


This article serves as a guide to the application registration process in Element451 from the student's viewpoint. It outlines three main scenarios: one for students without a record, another for those with a record but no password set, and a third for those with an existing account and password.

For more details on configuring your application registration form, refer to our Creating + Managing Applications help article.

Step-by-Step: Application Registration Form

  1. The student accesses your Application Site.

  2. They click Start Application and select the relevant application.

  3. The registration form for that specific application opens.

  4. The student completes the form fields.

  5. They click Create Account.

  6. Element451 then checks if the email address is associated with an existing record in your Element451 instance. Below, we'll outline what happens next in each scenario:

    • Scenario 1: No email match/no record exists

    • Scenario 2: Email was found; student does not have password set

    • Scenario 3: Email was found; student has a password set

Scenario 1: Students Without a Record in Element451

Students without a record simply complete the registration form for the desired application, enabling them to create a password and proceed with their application.

  • After clicking Create Account, the student is redirected to the application dashboard to begin completing the application.

Scenario 2: Students With a Record in Element451 & No Password Set

Students may unknowingly fall into this scenario, particularly when records are generated through various means such as data imports, form completions, event registrations or appointments. Since they haven't completed the application registration process, they might not be aware of their existing record in Element451. In such cases, the system initiates an email verification step to confirm their identity before proceeding with the application. This verification process ensures security and clarity, preventing confusion associated with password resets when no password has been set.

  1. Email Verification Triggered: If the email is found but no password is set, the system will automatically prompt an email verification step. The system sends an email to the student's email address with a verification code. This step is crucial for confirming the student’s identity and preventing unauthorized access.

  2. Verification Code Entry: To proceed, the student needs to retrieve this code from their email. Once they have the code, they should return to the application portal and enter it to complete the verification process.

  3. After confirming their identity, they are seamlessly redirected to the application site to begin their application.

Scenario 3: Students With a Record in Element451 (Has Account + Password)

In this situation, Element451 identifies a pre-existing record associated with the same email address, where a password has been set, indicating the creation of an account in the past. Consequently, we present the student with a message informing them of the existing profile. They are then presented with three choices:

  • Back to registration: Allows them to adjust their information

  • Go to login page: Allows them to log in using their password

  • Reset your password: Allows them to reset their password If they've forgotten it

    • For a student to receive the password reset email, the User Password Reset Request autoresponder message must be active in your application settings (Applications > Applications > Application Settings).

Did this answer your question?