Candidacy: Sign-up user journeys
Depending on the configurations, there are different frontend end-user journeys when signing up in Candidacy. Thus, this page provides an overview of all these different flows based on the various combinations of configurations.
Refer to the page Configuration (Candidacy) for more information regarding Candidacy’s configurations
This guide looks at the combination of the following configurations:
Requirement of proving identity
Parties
Candidate and party registration phases
The following images represent the screens that an end-user can see (at one point or another of their journey):
Sign-up
Candidate form
Prove identity
User panel
Finally, the two tables below show all the end-user journeys and their corresponding configurations. The first table is without Parties, while the scenarios in the second table, the Parties feature is enabled.
1. Configurations without Parties
Base Configurations | Variants | End-user Journeys *refer to the images above for visual aid |
|---|---|---|
For these scenarios, all phases are enabled | Identity is not required | The sign-up leads to the candidate form (ie. to create a candidate profile). |
Identity is required only for creating an account | The sign-up leads the end-user to prove their identity, and then goes into the candidate form. | |
Identity is required for creating an account and registering as a candidate | The sign-up leads the end-user to prove their identity, and then goes into the candidate form. | |
Identity is required only for registering as a candidate | The sign-up leads the end-user to prove their identity, and then goes into the candidate form. |
2. Configurations with Parties
Base Configurations | Variants | End-user Journeys *refer to the images above for visual aid |
|---|---|---|
For these scenarios, identity is not required, and parties are enabled | All phases enabled | The sign-up leads straight into the user panel, and from here, the end-user has the option of creating a candidate profile, a party profile, and/or joining a party). |
Only the party registration phase is disabled, and the rest are enabled | The sign-up leads the end-user to the candidate form, where they create their candidate profile. From here, they can join a party. | |
Only the candidate registration phase is disabled, and the rest are enabled | The sign-up leads straight into the user panel, and from here, the end-user has the option of creating a party profile, and/or joining a party). | |
Candidate and party registration phases are disabled | The sign-up leads straight into the user panel, and from here, they can only join a party. | |
For these scenarios, identity is only required for creating an account, and parties are enabled | All phases are enabled | The sign-up leads the end-user to prove their identity, and then goes straight to the user panel. From the user panel, the end-user can create a candidate profile and a party profile, as well as join a party. |
Only the party registration phase is disabled, and the rest are enabled | The sign-up leads the end-user to prove their identity, and then goes into the candidate form. After creating their profile, the end-user can join a party. | |
Only the candidate registration is disabled, and the rest are enabled | The sign-up leads the end-user to prove their identity, and then goes straight to the user panel. From the user panel, the end-user can create and/or join a party. | |
For these scenarios, identity is only required for registering as a candidate, and parties are enabled | All phases are enabled | The sign-up leads the end-user to prove their identity, and then goes straight to the user panel. From the user panel, the end-user can create a candidate profile and a party profile, as well as join a party. |
Only the party registration phase is disabled, and the rest are enabled | The sign-up leads the end-user to prove their identity, and then goes into the candidate form. After creating their profile, the end-user can join a party. | |
Only the candidate registration phase is disabled, and the rest are enabled | The sign-up leads the end-user to prove their identity, and then goes straight to the user panel. From the user panel, the end-user can create and/or join a party. | |
For these scenarios, identity is only required for creating a party (parties are enabled) | All phases are enabled | The sign-up leads the end-user to the candidate form. Afterwards, the end-user can join a party. To create a party, they need to prove their identity and access the party form in the user panel. |
Only the party registration phase is disabled, and the rest are enabled | The sign-up leads straight into the candidate form. Afterwards, the end-user can join a party. | |
Only the candidate registration phase is disabled, and the rest are enabled | The sign-up leads the end-user to prove their identity, and then into the user panel. From the user panel, the end-user can then create a party. | |
Identity is required for creating an account and registering as a candidate Parties are enabled | All phases are enabled | The sign-up leads the end-user to prove their identity, and then into the user panel. From there, they can create a candidate profile and a party profile, as well as join a party. |
Only the party registration phase is disabled, and the rest are enabled | The sign-up leads the end-user to prove their identity, and then into the candidate form. Afterwards, they can join a party. | |
Only the candidate registration phase is disabled, and the rest are enabled | The sign-up leads the end-user to prove their identity, and then into the user panel. From there, they can create and/or join a party. | |
Identity is required for creating an account and creating a party Parties are enabled | All phases are enabled | The sign-up leads the end-user to prove their identity, and then into the user panel. From there, they can create a candidate profile and a party profile, as well as join a party. |
Only the party registration phase is disabled, and the rest are enabled | The sign-up leads the end-user to prove their identity, and then into the candidate form. Afterwards, they can join a party. | |
Only the candidate registration phase is disabled, and the rest are enabled | The sign-up leads the end-user to prove their identity, and then into the user panel. From there, they can create and/or join a party. | |
Candidate and party registration phases are disabled | End-users are not able to sign up | |
Identity is required for registering as a candidate and creating a party Parties are enabled | All phases are enabled | The sign-up leads the end-user to prove their identity, and then into the user panel. From there, they can create a candidate profile and a party profile, as well as join a party. |
Only the party registration phase is disabled, and the rest are enabled | The sign-up leads the end-user to prove their identity, and then into the candidate form. Afterwards, they can join a party. | |
Only the candidate registration phase is disabled, and the rest are enabled | The sign-up leads the end-user to prove their identity, and then into the user panel. From there, they can create and/or join a party. | |
Identity is required for all three: creating an account, registering as a candidate, and creating a party Parties are enabled | All phases are enabled | The sign-up leads the end-user to prove their identity, and then into the user panel. From there, they can create a candidate profile and a party profile, as well as join a party. |
Only the party registration phase is disabled, and the rest are enabled | The sign-up leads the end-user to prove their identity, and then into the candidate form. Afterwards, they can join a party. | |
Only the candidate registration phase is disabled, and the rest are enabled | The sign-up leads the end-user to prove their identity, and then into the user panel. From there, they can create and/or join a party. |