OpenText Directory Services - OpenText eDOCS Integration and Automation

Common Integration Use Cases Between OpenText Directory Services and OpenText eDOCS

1. Centralized user and group provisioning for eDOCS access

Data flow: OpenText Directory Services to OpenText eDOCS

Synchronize user accounts, security groups, and role assignments from OpenText Directory Services into OpenText eDOCS so legal and professional services teams receive consistent access without manual setup. This supports rapid onboarding, reduces help desk tickets, and ensures that matter and document permissions reflect current organizational structure.

Business value: Faster user provisioning, fewer access errors, and lower administrative overhead.

2. Matter-based security group mapping

Data flow: Bi-directional, with OpenText Directory Services as the identity source and OpenText eDOCS as the document repository

Use directory groups to drive matter-level security in eDOCS, such as assigning access to litigation teams, deal teams, or client-specific groups. When a user is added to or removed from a directory group, eDOCS permissions update accordingly, helping legal teams maintain strict confidentiality and least-privilege access.

Business value: Stronger document security, reduced risk of unauthorized access, and easier management of sensitive matters.

3. Automated onboarding and offboarding for legal staff and contractors

Data flow: OpenText Directory Services to OpenText eDOCS

When HR or IT updates a user in OpenText Directory Services, the integration can automatically create, modify, or disable the corresponding eDOCS account. New attorneys, paralegals, and contract staff gain timely access to the correct matters, while departing users are removed immediately to protect confidential content.

Business value: Improved compliance, reduced security exposure, and faster employee lifecycle management.

4. Role-based access aligned to practice groups and client teams

Data flow: OpenText Directory Services to OpenText eDOCS

Map directory roles such as partner, associate, paralegal, records manager, or client service team member to predefined eDOCS permissions. This allows firms and legal departments to standardize access policies across offices and practice areas while minimizing manual permission changes for each matter.

Business value: Consistent access governance, simplified administration, and better audit readiness.

5. Single sign-on for legal document access

Data flow: OpenText Directory Services to OpenText eDOCS

Use OpenText Directory Services as the authentication and identity backbone for eDOCS so users can access documents with their corporate credentials. This reduces password fatigue, improves user adoption, and supports a smoother experience for attorneys and support staff working across multiple systems.

Business value: Better user experience, fewer password reset requests, and stronger identity control.

6. Automated access review and certification for active matters

Data flow: Bi-directional

Pull current eDOCS matter access lists into OpenText Directory Services or a connected governance process for periodic review by practice leads or records managers. Approved changes can then be pushed back to eDOCS to remove stale access, especially for long-running litigation or transaction matters with changing team composition.

Business value: Improved access governance, reduced entitlement creep, and stronger audit compliance.

7. Cross-office and cross-department collaboration with controlled access

Data flow: OpenText Directory Services to OpenText eDOCS

Support collaboration across offices, regions, and legal departments by using directory-managed groups to grant temporary or project-based access to eDOCS matters. This is useful for large transactions, investigations, or regulatory responses where teams need quick access without permanent permission changes.

Business value: Faster collaboration, less manual coordination, and better control over temporary access.