Salesforce Commerce Cloud (SFCC) - OpenText Directory Services Integration and Automation

Common Integration Use Cases Between Salesforce Commerce Cloud and OpenText Directory Services

1. Centralized shopper and employee identity synchronization

OpenText Directory Services can act as the authoritative identity store for users, groups, and roles, while Salesforce Commerce Cloud consumes that data to control access to storefront administration, merchant tools, and customer service functions. This reduces duplicate user provisioning and ensures that access rights are aligned with corporate identity standards.

• Direction: OpenText Directory Services to Salesforce Commerce Cloud
• Business value: Faster onboarding and offboarding, fewer access errors, stronger governance

2. Role-based access control for commerce operations teams

Commerce organizations often need different permissions for merchandisers, content editors, customer service agents, and regional administrators. OpenText Directory Services can maintain group membership and role assignments, which SFCC can use to grant the correct level of access by team, region, or brand.

• Direction: OpenText Directory Services to Salesforce Commerce Cloud
• Business value: Consistent access control across markets and teams, reduced security risk

3. Automated user provisioning for seasonal and temporary staff

Retailers frequently onboard temporary staff for peak seasons, promotions, and campaign launches. By integrating OpenText Directory Services with Salesforce Commerce Cloud, user accounts and permissions can be created, updated, and removed automatically based on directory changes, avoiding manual administration during high-volume periods.

• Direction: OpenText Directory Services to Salesforce Commerce Cloud
• Business value: Lower administrative effort, faster readiness for peak trading periods, improved compliance

4. Single sign-on for internal commerce users

OpenText Directory Services can support centralized authentication for internal users who manage SFCC storefronts, catalogs, promotions, and orders. This enables single sign-on across enterprise applications and reduces password fatigue for business users working across multiple systems.

• Direction: Bi-directional authentication alignment, with OpenText Directory Services as identity source
• Business value: Better user experience, fewer login issues, improved productivity

5. Regional administration and delegated access management

Global retailers often operate multiple brands and country sites with different operational teams. OpenText Directory Services can maintain region-specific groups that SFCC uses to delegate access to local merchandisers and support teams without exposing global administration functions.

• Direction: OpenText Directory Services to Salesforce Commerce Cloud
• Business value: Supports decentralized operations while preserving centralized control

6. Access revocation when employees change roles or leave the company

When an employee changes department or exits the organization, updates in OpenText Directory Services can automatically remove or adjust their Salesforce Commerce Cloud permissions. This helps prevent unauthorized access to commerce operations, customer data, and order management functions.

• Direction: OpenText Directory Services to Salesforce Commerce Cloud
• Business value: Stronger security posture, reduced audit findings, lower risk of orphaned accounts

7. Shared identity governance for commerce support workflows

Customer service and operations teams often need access to SFCC order data, customer profiles, and fulfillment exceptions. OpenText Directory Services can provide a governed identity framework so that only approved support groups receive access, with permissions tied to business roles and approval workflows.

• Direction: OpenText Directory Services to Salesforce Commerce Cloud
• Business value: Better control over sensitive commerce data, clearer accountability, easier audits