Consonance - OpenText Identity and Access Management Integration and Automation

Common Integration Use Cases Between Consonance and OpenText Identity and Access Management

1. Centralized user provisioning for publishing teams

Data flow: OpenText Identity and Access Management ? Consonance

When new employees, contractors, or agency partners are added in the enterprise identity system, their accounts and role assignments can be automatically provisioned in Consonance. This ensures editors, production staff, rights managers, and project coordinators receive the correct access on day one without manual setup.

• Automatically create Consonance user accounts from approved identity records
• Assign role-based access by department, imprint, or business unit
• Reduce onboarding delays for editorial and production workflows
• Lower security risk by eliminating ad hoc account creation

2. Automated deprovisioning for offboarding and contractor expiry

Data flow: OpenText Identity and Access Management ? Consonance

When an employee leaves the organization or a contractor?s engagement ends, access to Consonance can be removed immediately based on identity lifecycle events. This protects unpublished manuscripts, royalty data, rights agreements, and sensitive title metadata from unauthorized access.

• Disable Consonance access when identity status changes to inactive
• Remove temporary access for freelancers and external collaborators on schedule
• Prevent orphaned accounts in editorial and production projects
• Support audit readiness and access governance requirements

3. Single sign-on for editorial, production, and rights users

Data flow: OpenText Identity and Access Management ? Consonance

Publishing staff can use a single corporate login to access Consonance, reducing password fatigue and improving productivity. This is especially valuable for teams that move between Consonance and other OpenText services or enterprise applications during the publishing cycle.

• Enable seamless access without separate Consonance credentials
• Improve user adoption across editorial, design, and rights teams
• Reduce help desk tickets related to password resets
• Strengthen authentication consistency across the enterprise

4. Role-based access control for sensitive publishing data

Data flow: Bi-directional, with OpenText Identity and Access Management enforcing roles and Consonance consuming role attributes

Consonance can use identity attributes such as job function, imprint, region, or business unit to control access to manuscripts, royalty records, rights contracts, and title metadata. This ensures users only see the projects and data relevant to their responsibilities.

• Restrict rights and royalty information to authorized personnel
• Limit access to specific imprints, territories, or title groups
• Support separation of duties between editorial, finance, and production teams
• Apply consistent access policies across cloud and hybrid environments

5. Secure external collaborator access for authors, freelancers, and vendors

Data flow: OpenText Identity and Access Management ? Consonance

Publishing organizations often work with external authors, copyeditors, illustrators, and production vendors. Identity and access management can govern temporary or limited-access identities for these users, allowing them to participate in Consonance workflows without exposing internal systems or unrelated projects.

• Issue time-bound access for external contributors
• Limit permissions to assigned manuscripts or tasks only
• Enforce stronger authentication for non-employee access
• Improve control over third-party participation in publishing workflows

6. Access governance for rights and royalty workflows

Data flow: OpenText Identity and Access Management ? Consonance

Rights and royalty processes often involve confidential commercial data. By integrating identity governance with Consonance, publishers can ensure only approved roles can view, edit, or approve rights agreements, royalty statements, and related metadata.

• Restrict royalty administration to finance and rights teams
• Require elevated access for contract approval or metadata changes
• Maintain traceable access controls for audit and compliance
• Reduce the risk of unauthorized changes to revenue-critical records

7. Audit and compliance reporting for publishing operations

Data flow: Consonance ? OpenText Identity and Access Management

Consonance activity logs can be correlated with identity records to show who accessed or changed manuscript, title, or rights data and under what role. This supports internal audits, compliance reviews, and investigations into workflow exceptions or data issues.

• Link user actions in Consonance to authenticated identities
• Support evidence collection for access reviews and audits
• Identify unusual access patterns across publishing teams
• Improve accountability for changes to critical title data

8. Faster cross-team workflow setup for new imprints, projects, and acquisitions

Data flow: Bi-directional

When a new imprint is launched or a publishing acquisition is completed, identity data can be used to rapidly establish access groups in Consonance for the relevant editorial, production, and rights teams. As organizational structures change, Consonance permissions can be updated automatically to match the new operating model.

• Accelerate setup for new publishing programs and imprints
• Align access with organizational changes after mergers or acquisitions
• Reduce manual administration during high-volume project launches
• Keep workflow access synchronized with enterprise identity structures