OpenText Directory Services - Kentico Integration and Automation

Common Integration Use Cases Between OpenText Directory Services and Kentico

1. Centralized user provisioning for Kentico site access

Data flow: OpenText Directory Services → Kentico

Synchronize employee, partner, or customer identities from OpenText Directory Services into Kentico to automatically create and update user accounts for portal access, authenticated content, and self-service experiences. This reduces manual account administration and ensures users always have the correct profile and access rights.

• Automatically provision new users when they are added to the directory
• Update names, email addresses, departments, and status changes in Kentico
• Disable Kentico access when a user is removed or deactivated in the directory

2. Role-based content access and personalization

Data flow: OpenText Directory Services → Kentico

Use directory groups and roles from OpenText Directory Services to control which content, pages, or digital assets users can access in Kentico. This supports secure intranet, partner portal, and customer portal scenarios where content must vary by audience segment.

• Map directory groups to Kentico roles and permissions
• Restrict sensitive documents, campaign assets, or product information by audience
• Deliver personalized page content based on department, region, or partner tier

3. Single sign-on for authenticated digital experiences

Data flow: OpenText Directory Services → Kentico

Integrate OpenText Directory Services as the identity source for single sign-on into Kentico, allowing users to access websites, portals, or internal digital experiences with their existing enterprise credentials. This improves user experience and reduces password-related support requests.

• Enable seamless login for employees and business partners
• Reduce password reset tickets and login friction
• Support secure access to authenticated Kentico content and workflows

4. Automated deprovisioning for compliance and access control

Data flow: OpenText Directory Services → Kentico

When a user is terminated, transferred, or no longer eligible for access in OpenText Directory Services, automatically remove or restrict their Kentico account. This helps enforce least-privilege access and supports audit and compliance requirements.

• Disable accounts immediately when directory status changes
• Remove access to restricted content and administrative functions
• Maintain consistent access governance across systems

5. Department and region-based content governance

Data flow: OpenText Directory Services → Kentico

Use organizational attributes from OpenText Directory Services such as department, location, or business unit to drive content governance in Kentico. This is useful for multinational organizations that need localized content ownership and approval workflows.

• Assign editors and approvers by business unit or geography
• Route content approvals to the correct regional teams
• Limit editing rights to specific organizational groups

6. Partner portal access management

Data flow: OpenText Directory Services → Kentico

For partner-facing portals built in Kentico, use OpenText Directory Services to manage partner identities and group memberships. This enables controlled access to sales tools, training materials, pricing documents, and co-branded content without maintaining separate user stores.

• Provision partner users based on directory membership
• Grant access by partner tier, contract status, or region
• Quickly revoke access when partner relationships change

7. User attribute synchronization for personalized marketing journeys

Data flow: OpenText Directory Services → Kentico

Pass trusted identity attributes from OpenText Directory Services into Kentico to improve audience segmentation and personalization. Kentico can then tailor content, offers, and calls to action based on verified user data rather than self-reported information.

• Use department, job title, or location for segmentation
• Personalize landing pages and campaign content for authenticated users
• Improve relevance of digital experiences for internal and external audiences

8. Directory-driven administration for Kentico content teams

Data flow: Bi-directional

Synchronize selected user and group changes between OpenText Directory Services and Kentico so content teams can be managed centrally while Kentico retains local role assignments for editorial workflows. This supports efficient administration across IT and marketing teams.

• Keep user identities aligned across both platforms
• Preserve Kentico-specific editorial roles while using directory-based identity management
• Reduce duplicate user maintenance and improve operational consistency