OpenText Directory Services - OpenText TeamSite - LiveSite Content Services Integration and Automation

Common Integration Use Cases Between OpenText Directory Services and OpenText TeamSite - LiveSite Content Services

1. Centralized user authentication for content authors and portal users

Data flow: OpenText Directory Services → OpenText TeamSite - LiveSite Content Services

Use OpenText Directory Services as the authoritative identity store for authenticating editors, approvers, and portal users accessing TeamSite and LiveSite experiences. This ensures consistent login credentials, reduces duplicate accounts, and simplifies access governance across digital teams.

• Single sign-on for content authors and business approvers
• Reduced password reset and account administration effort
• Consistent access policies across publishing and delivery environments

2. Role-based access control for content management workflows

Data flow: OpenText Directory Services → OpenText TeamSite - LiveSite Content Services

Synchronize directory groups into TeamSite roles such as author, reviewer, publisher, and site administrator. This allows access rights to be managed centrally in the directory while TeamSite enforces permissions based on business roles.

• Faster onboarding and offboarding of content staff
• Lower risk of unauthorized publishing activity
• Cleaner separation of duties for regulated content operations

3. Personalized content delivery based on user attributes

Data flow: Bi-directional

TeamSite can use identity attributes from OpenText Directory Services such as department, region, language, or customer segment to render personalized content in LiveSite. In return, TeamSite can capture user interaction preferences or profile updates and pass them back to the directory or connected identity layer where appropriate.

• Region-specific or role-specific web content
• Improved customer and employee digital experience
• More relevant messaging without maintaining separate sites

4. Secure intranet and partner portal access

Data flow: OpenText Directory Services → OpenText TeamSite - LiveSite Content Services

For employee intranets or partner portals built on LiveSite, directory-based authentication ensures only approved users can access internal content. Directory groups can be mapped to portal sections so that users see only the content relevant to their organization, geography, or partner tier.

• Controlled access to confidential documents and announcements
• Segmented portal experiences for employees, dealers, or distributors
• Reduced need for custom access logic in the portal layer

5. Automated content approval routing based on organizational structure

Data flow: OpenText Directory Services → OpenText TeamSite - LiveSite Content Services

Use directory attributes such as manager, team, location, or business unit to drive approval workflows in TeamSite. Content can be routed automatically to the correct reviewers and approvers based on the author’s organizational context or the content category.

• Shorter publishing cycles
• Less manual workflow configuration
• Better alignment between content governance and business ownership

6. Dynamic audience targeting for campaigns and announcements

Data flow: OpenText Directory Services → OpenText TeamSite - LiveSite Content Services

Marketing, HR, or corporate communications teams can target announcements to specific audiences defined in the directory, such as sales teams, executives, contractors, or regional offices. LiveSite can then deliver the right banner, article, or call to action to each audience segment.

• More precise internal and external communications
• Higher engagement with targeted content
• Less duplication of campaign assets across multiple pages

7. Lifecycle management for user access and content administration

Data flow: OpenText Directory Services → OpenText TeamSite - LiveSite Content Services

When users join, move roles, or leave the organization, directory updates can automatically adjust their TeamSite permissions. This supports joiner, mover, leaver processes and reduces the risk of stale accounts retaining publishing access.

• Improved security and compliance
• Lower administrative overhead for IT and web operations
• Faster access changes during reorganizations

8. Unified governance for multi-team digital operations

Data flow: Bi-directional

Combine directory-managed identities with TeamSite content governance to create a controlled operating model for web, intranet, and portal teams. Directory data defines who can create, approve, and publish content, while TeamSite activity can be used to support audit trails and operational reporting.

• Clear accountability across content, security, and IT teams
• Better audit readiness for regulated industries
• Consistent governance across multiple sites and business units