Registers the authenticators a member needs according to the application's registration settings, and associates the member with their organization
This step registers the authentication methods a member needs, based on the registration settings defined for the application. It evaluates what the member has already registered and asks only for what's missing, so it can be placed in any flow without checking the member's state beforehand.
Use this step after Authenticate Member, typically in a member invite flow or a login flow that has to bring members up to date with the application's registration requirements.
This step runs in SSO journeys, on Mosaic-hosted experiences using Mosaic branding and styling management. It isn't available in SDK-driven journeys.
When triggered, the step:
- Receives the organization email as an input.
- Loads the registration settings that apply—which authentication methods the application marks as Required and which as Optional.
- Ensures the member exists under the application.
- Evaluates which of those methods the member has already registered, and skips them.
- Registers the outstanding required methods, then offers the outstanding optional ones.
- Associates the member with the organization.
Registration settings are defined per method in the B2B tab of the application, where each method is marked Required, Optional, or Hidden for registration. See Configure B2B application settings. Methods marked hidden aren't offered.
Members complete every required method before any optional method is offered. Required methods are presented one at a time, and the member can't continue past one until it's registered. Optional methods follow, and each can be skipped and left for later.
If the member already satisfies the registration settings, the step completes without presenting anything.
Members of federated organizations aren't asked to register anything—credentials are managed by the organization's Identity Provider. The step completes immediately.
Organization selection doesn't occur during or after registration. It applies only after authentication, where an existing member may be associated with more than one organization. See Authenticate Member.
The step registers the completed authenticators to the member's record. The methods the member registered are part of the step's outcome, so a later step in the journey can act on them.
The step succeeds once every required method is registered, and fails where a required method isn't completed within the permitted retries. Failure of an optional method doesn't fail the step—the step continues and completes as a success. Failures are reported using the platform conventions for registration errors—see Journey errors.
| Field | Description |
|---|---|
| Organization (Email) | The email associated with the organization being targeted. Collect it before this step—for example, using the Collect Information step—and pass it to the step directly. It isn't taken from the journey context. |
| Error Output Variable | Name of the variable that stores any errors returned by the step |
| Failure Behavior | Determines the behavior in case of failure, which either aborts the journey or proceeds to a failure branch of the control flow (default). |
This step can be configured to record step input and output data, or a custom payload, which is then surfaced in journey events in Journey Analytics for diagnostic purposes. For details, see Additional data reporting.
Consider a member invite flow. An organization admin adds a member, who receives an invitation and follows the link into the journey. The journey authenticates them with Authenticate Member, then invokes Register Member Authenticators with the same organization email.
Suppose the application marks password as required for registration, passkey as required, and TOTP as optional. A member who has already registered a password is asked only for the passkey, and is then offered TOTP with the option to skip it. Once the passkey is registered, the step succeeds—whether or not the member registered TOTP.