Home | Connectors | Consonance | Consonance - OpenText Directory Services Integration and Automation

Consonance - OpenText Directory Services Integration and Automation

Integrate Consonance Marketing and OpenText Directory Services Security / Identity Access Management apps with any of the apps from the library with just a few clicks. Create automated workflows by integrating your apps.

Common Integration Use Cases Between Consonance and OpenText Directory Services

1. Automated user provisioning for publishing teams

Data flow: OpenText Directory Services to Consonance

Synchronize employee, contractor, and agency user accounts from OpenText Directory Services into Consonance so editorial, production, rights, and finance teams receive access automatically when they join a project or imprint. This reduces manual account setup, speeds onboarding, and ensures users only see the titles and workflows relevant to their role.

  • Provision editors, designers, production managers, and rights staff based on directory group membership
  • Assign Consonance roles aligned to job function and imprint
  • Disable access in Consonance when a user is removed from the directory

2. Role-based access control for manuscript and title workflows

Data flow: Bi-directional

Use directory groups from OpenText Directory Services to drive role assignments in Consonance, such as editorial reviewer, production approver, or rights administrator. Consonance can return workflow status or project membership to support access decisions, ensuring users only participate in the stages they are authorized to handle.

  • Restrict manuscript access by imprint, region, or project team
  • Separate permissions for internal staff, freelancers, and external partners
  • Support least-privilege access for sensitive acquisitions and rights data

3. Centralized identity management for multi-imprint publishing operations

Data flow: OpenText Directory Services to Consonance

For publishers operating multiple imprints or business units, directory synchronization can map organizational structure into Consonance. This allows each imprint to maintain its own workflow teams while using a single identity source, improving governance and reducing duplicate user administration across the publishing portfolio.

  • Map directory groups to imprint-specific Consonance workspaces
  • Standardize access policies across all publishing brands
  • Simplify administration during reorganizations or imprint mergers

4. Contractor and agency access for editorial and design collaboration

Data flow: OpenText Directory Services to Consonance

Publishers often work with freelance editors, cover designers, indexers, and proofreaders. By managing these external identities in OpenText Directory Services and syncing them to Consonance, teams can grant time-bound access to specific titles, while keeping external collaborators out of broader internal systems.

  • Create temporary accounts for project-based contributors
  • Limit access to assigned manuscripts, assets, and tasks only
  • Automatically revoke access at contract end or project completion

5. Secure rights and royalty workflow access

Data flow: OpenText Directory Services to Consonance

Rights and royalty operations often require tighter controls than standard editorial workflows. Integrating directory-based identity and group management with Consonance enables publishers to separate rights administrators, royalty analysts, and finance approvers from general publishing users, reducing the risk of unauthorized access to sensitive contract and payment information.

  • Grant access to rights records only to authorized legal or rights staff
  • Limit royalty reporting to finance and designated managers
  • Support audit-ready access governance for sensitive business data

6. Automated deprovisioning when staff leave or change roles

Data flow: OpenText Directory Services to Consonance

When an employee changes department or leaves the organization, OpenText Directory Services can trigger immediate updates in Consonance to remove or adjust access. This prevents former staff from retaining visibility into unpublished titles, contracts, or production schedules and reduces security and compliance risk.

  • Remove access to active projects when employment ends
  • Update permissions when users move from editorial to production or sales
  • Maintain a clean audit trail for access changes

7. Publisher-wide audit and compliance support

Data flow: Bi-directional

Combine directory records with Consonance workflow activity to support audits of who accessed which title, when permissions were granted, and which teams handled sensitive content. This is especially useful for publishers that need to demonstrate control over embargoed manuscripts, licensed content, and royalty-related data.

  • Link user identity to workflow actions and approvals
  • Track access to confidential manuscripts and contracts
  • Support internal audits and compliance reviews

8. Streamlined access for distributed and remote publishing teams

Data flow: OpenText Directory Services to Consonance

For publishers with remote staff across editorial, production, and marketing, directory synchronization ensures users can access Consonance securely from day one without manual setup delays. This improves productivity for distributed teams working across time zones and accelerates collaboration on time-sensitive publishing schedules.

  • Enable consistent access across offices and remote locations
  • Reduce help desk requests for account creation and permission changes
  • Improve turnaround time for manuscript and production workflows

How to integrate and automate Consonance with OpenText Directory Services using OneTeg?