Organization step

The Organization step appears at the beginning of the registration journey when the application is configured to support organizations.

When accounts are unique to an organization, the step prompts the customer to enter an organization route before proceeding. If the option is enabled, customers can also choose to create a new organization directly from this screen. After creating an organization, the registration flow continues with the next step in the journey.

Customers encounter one of the following screens:

• A screen asking for the Organization route, which is a unique identifier for their organization.

  

• If creation is enabled, a button to Create a new organization will be available. Selecting this opens a form where customers can enter:

  • The organization name
  • A custom organization route

Once submitted, the new organization is created and associated with the customer account being registered.

Settings that affect this step

Whether and how the organization step appears in the registration journey depends on several configuration options:

• Application configuration: The step appears only for applications that are enabled for organizations (Organization-only and Hybrid).
• Identifier uniqueness and base organization: Whether the Organization step requires a route before logging in depends on how the application's base organization and identifier uniqueness settings are configured.
  • If the application has a base organization and that organization is set to Account identifiers are unique to this organization and its descendants, the organization route is skipped. The system will infer the organization route from the base organization, and the customer will not be prompted to enter one.
  • If the base organization is set to Account identifiers are unique to this organization, the organization route is required. This allows the customer to select or create the specific organization they belong to.
  • If no base organization is set, the organization route is also required.
• Self-service settings in the organization: Determines whether self-service registration into the organization or the creation of new child organizations is possible.
• Identity store settings: Determines whether new organizations without a parent organization can be created during registration.
• Organization roles: A default organizational role can be applied to the customer or admin who created the organization. A different role can be applied to any future accounts that self-service register into the organization.
• Branding policy: Controls the appearance and text shown on the organization screen.

What happens next

After the organization is identified or created, the rest of the registration journey continues, typically with collecting personal information or entering credentials in the Account registration step.

Extensibility points

After the Organization step, the following extensibility points are available:

After customer identification: This event is triggered once the customer has provided their identifier (email address, username, or phone) and before they are asked for any factor of authentication. This hook can be used to step up or step down the login flow based on an external event, risk data from an external system, or other customer account attribute information. Synchronous hook.

After external login: This hook can trigger an event or retrieve data from an external system after a customer registers or logs in with a social login provider, potentially affecting the flow. Synchronous hook.