The registration journey in Strivacity guides customers through the steps required to create and activate an account. This process includes several steps designed to collect and verify the necessary information while ensuring a secure and user-friendly experience.

1. App launch: The registration process begins when a customer launches the application, either through self-service or by accepting an invitation.
2. Organization: This step involves identifying the organization the customer is associated with in B2B use cases, which includes selecting an organization or automatically identifying it based on certain criteria.
3. Account registration: The customer completes the registration form by creating an identifier and password, providing the required and optional attributes configured in the application's identity store, and accepting consents.
   1. Identifier: The customer creates a unique identifier to represent their account.
   2. Password: The customer creates and confirms a password for the account.
   3. Account attributes: The customer enters the required and optional attributes that will be stored in their account record.
   4. Consents: Any mandatory or optional consents will be presented and collected here.
4. Identity verification: After registration, customers may be required to undergo identity verification to ensure that their identity matches the information provided. This workflow is defined by the identity verification policy.
5. MFA enrollment: MFA enrollment is prompted, enabling an additional layer of security by linking an additional authentication method to the customer’s account.
6. Account activation: Following MFA enrollment, the account activation step (if configured) finalizes the registration process by verifying an email or phone identifier before allowing a customer to log in. Account activation marks the transition from registration to an active, usable account state. There are two options available in the self-service registration settings: in-band activation (OTP via phone or email) and out-of-band activation (magic link via email).
7. OIDC token or SAML2 response generation: Upon successful registration and activation, an OIDC token or a SAML2 response is generated to facilitate secure authentication.
8. Redirect: Finally, the customer is redirected to the appropriate destination based on the organization’s configuration, completing the registration journey.

Extensibility points

Strivacity's customer journeys have various points where custom Journey Builder workflows and Lifecycle Event Hooks can be inserted to extend the natively configured workflows. These extensibility points are triggered by various events that happen during the customer journey.

There are two types of hooks: synchronous, which pauses Strivacity’s workflow until the script completes execution, and asynchronous, which runs the script without interrupting the workflow.

In the registration journey, the following extensibility points are available: