The Identify step is responsible for determining which customer is trying to access a brand portal. In B2B use cases, this step can also identify which organization the customer belongs to. The identification of the customer or organization may impact which policies and configurations apply to them.

The Identify step is composed of multiple screens that guide the customer through selecting an identifier type (such as email, phone, or username) and entering their credentials. Each screen plays a role in confirming the customer's identity before moving on to authentication.

1. Organization identification: Allows customers to input their organization's unique route to access the correct login experience. This ensures that customers are directed to the appropriate organization for authentication and account management.
2. Local identity: Facilitates customer authentication by enabling them to either provide their unique identifiers, such as a username, email address, or phone number (Identity input), or select from a list of remembered accounts (Account chooser) for seamless login. This step can also be used for organization routing if using Identifier-based routing
   1. Identity input: allows customers to enter their unique identifier, such as a username, email address, or phone number, to begin the login process.
   2. Account chooser: displays a list of remembered accounts from previous sessions, enabling customers to select an account to log in without re-entering their identifier.
3. External identity: Third-party identity providers (such as social logins) are supported, enabling customers to authenticate with external credentials.
4. Account linking: Strivacity enables linking external and local accounts allowing customers to connect their user accounts to external identity providers.

Extensibility points

During the Identify step, the following extensibility points are available:

To learn more about extensibility points, refer to the Lifecycle event hooks documentation.