OpenText Directory Services - PoolParty Semantic Suite Integration and Automation

Common Integration Use Cases Between OpenText Directory Services and PoolParty

1. Role-Based Access to Semantic Taxonomies

Data flow: OpenText Directory Services → PoolParty

Synchronize users, groups, and role assignments from OpenText Directory Services into PoolParty so semantic taxonomy management can be restricted by business role. For example, only content governance teams can edit controlled vocabularies, while regional teams can view and propose terms. This reduces unauthorized changes, improves taxonomy quality, and supports segregation of duties.

2. User and Group Synchronization for Knowledge Management Workspaces

Data flow: OpenText Directory Services → PoolParty

Provision PoolParty workspaces, project spaces, and collaboration groups based on directory identities and organizational structure. When employees join a department or project team, their access to relevant semantic models, classification projects, and knowledge graph initiatives is automatically assigned. This lowers manual administration and ensures teams always work with the correct knowledge assets.

3. Semantic Content Classification Based on Organizational Context

Data flow: OpenText Directory Services → PoolParty

Use directory attributes such as department, location, job function, or business unit to drive content classification rules in PoolParty. For instance, documents created by legal users can be tagged with legal domain concepts, while marketing users? content can be enriched with campaign and product taxonomy terms. This improves search relevance and makes downstream content discovery more accurate.

4. Personalized Search and Discovery by User Profile

Data flow: OpenText Directory Services → PoolParty

Pass authenticated user identity and group membership from OpenText Directory Services to PoolParty-enabled search experiences so results can be ranked or filtered by role, department, or region. A sales user can see customer-facing product knowledge first, while compliance users see policy and regulatory content. This increases productivity by surfacing the most relevant information for each user group.

5. Governance of Taxonomy Approval Workflows

Data flow: Bi-directional

Use OpenText Directory Services to identify approvers and reviewers, and use PoolParty to manage the semantic review workflow for new terms, synonyms, and concept changes. Subject matter experts can submit taxonomy updates, while designated approvers from compliance, legal, or product teams receive tasks based on directory roles. This creates a controlled governance process for enterprise vocabulary management.

6. Automated Access Provisioning for Semantic AI Projects

Data flow: OpenText Directory Services → PoolParty

When new semantic AI or knowledge graph projects are launched in PoolParty, automatically provision access for project members based on directory groups. This is useful for enterprise initiatives such as product catalog enrichment, policy classification, or customer knowledge graphs. It speeds project onboarding and ensures only authorized users can work on sensitive datasets.

7. Audit and Accountability for Knowledge Asset Changes

Data flow: PoolParty → OpenText Directory Services

Send change events from PoolParty, such as taxonomy edits, concept merges, or ontology updates, back to directory-linked audit processes for accountability and reporting. By associating changes with authenticated users and groups, organizations can track who modified critical knowledge structures and when. This supports governance, compliance, and operational transparency.

8. Enterprise Knowledge Segmentation Across Business Units

Data flow: Bi-directional

Combine directory-based organizational data with PoolParty semantic models to maintain separate but consistent knowledge structures for different business units, regions, or brands. For example, a global enterprise can manage a shared core taxonomy while allowing local teams to access only their relevant extensions. This balances standardization with local flexibility and reduces duplication across teams.