Identity

Identity manages users, organizations, authentication, and access across Commerce ecosystem to secure tools and data based on organization, persona, and working context.

Identity is the foundational capability that manages users, organizations, authentication, and access across Commerce ecosystem. The primary purpose of this capability is to ensure that each person can securely access appropriate tools and data based on organization, persona, and working context.

Benefits

Identity provides administrative capability to scale and secure access tracking through the following features:

  • Structured account management: Supports root, parent, and child organizations so that teams can model customer hierarchies instead of managing access on an individual basis.

  • Secure and compliant access: Centralizes authentication and password recovery while supporting regional requirements for personal data processing.

  • Efficient onboarding and administration: Helps administrators create organizations, onboard business users, assign personas, and set active organization context without workaround tasks.

  • Improved user continuity: Supports guest access, user login, password reset, and session handling so that users can transition from anonymous to authenticated experiences with minimal friction.

  • Context-aware productivity: Uses active organization and persona assignment to tailor visible options, actions, and data scopes.

Data flow

Identity configuration begins with tenant setup tasks, where an authorized user creates a root organization and an initial system administrator. From that point, administrators define additional organizations, create business users, assign personas, and establish organization context. Users then sign in securely, recover access if required, and operate within the designated organizational scope.

Solving Business Challenges with Identity

Use this guide to translate business needs into configuration actions and delivery tasks.

Business objective Recommended capability Operational task Data flow logic
Establish secure tenant and administrator setup Identity foundation and administrator onboarding
  1. Create the initial system administrator and root organization.
  2. Define the required parent organization structure.
  3. Create the first managed organizations.
 Set up the tenant foundation first, create the root organizational structure, and onboard the first administrator so that downstream elements inherit a governed model.
Manage customer organizations and business users at scale Organization management and business user lifecycle
  1. Create the organization structure.
  2. Assign users to the correct organization.
  3. Create and manage business users in the administration tool.
 Create the organization hierarchy, place each user in the right organization, and manage that user within the correct business context to maintain orderly asset ownership.
Control what users can access and act on Persona assignment and active organization context
  1. Assign personas to users.
  2. Review persona details and allowed actions.
  3. Apply role-based access in the right organization context.
 Assign a persona to define responsibilities, then apply active organization context so that the user interface filters content to match the active scope.
Support secure day-to-day access Authentication, password recovery, and session management
  1. Provide password reset through email links.
  2. Support guest access where appropriate.
  3. Apply session timeout and persistence rules.
 Allow users to begin as guests when appropriate, enforce authentication when required, provide email recovery options, and apply timeout rules to protect user sessions.

Prerequisites

Before you begin, verify that the following requirements are met:

  • Permission level: Administrator or implementation team access for tenant setup, organization management, and persona assignment.

  • System requirements: Auth0-backed authentication environment and Commerce tenant configuration capable of supporting organization and user management.

  • Data requirements: Initial tenant information, root organization details, administrator identity configurations, organizational hierarchy definitions, and business user profiles for onboarding.

Technical Details

This capability is built on an identity framework that uses Auth0 for authentication and supports organization-aware user management. The underlying model requires one root organization per tenant, supports parent-child organization structures, and uses a combination of assigned personas and organizational context to govern resource visibility.

Review the following core implementation factors:

  • Users are linked with specific organizations and require active organization context parameters to scope data permissions accurately.

  • Password recovery operations rely on email-based reset flows.

  • Session rules manage timeout properties and guest-to-authenticated identity state transitions.

  • Data architectures must account for regional compliance rules regarding personal data processing.

  • Identity design patterns must allow future expansion for additional access control matrices and sales channel scopes.