Acquia DAM (Widen) - OpenText Core Signature Integration and Automation

Common Integration Use Cases Between Acquia DAM (Widen) and OpenText Core Signature

Acquia DAM (Widen) and OpenText Core Signature complement each other well in organizations that manage branded content, approvals, and document workflows. Acquia DAM centralizes approved assets and brand materials, while OpenText Core Signature adds legally binding electronic signature capabilities for documents that require formal approval. Together, they help teams move faster, reduce manual handoffs, and maintain control over brand and compliance-sensitive content.

1. Brand Asset Approval Sign-Off for Final Creative Materials

Flow: Acquia DAM to OpenText Core Signature

Marketing and creative teams can route final versions of high-value assets such as campaign visuals, product brochures, packaging artwork, or brand guidelines from Acquia DAM into OpenText Core Signature for formal approval. Once signed, the approved version and signature certificate can be stored back in Acquia DAM as the authoritative record.

Business value: Creates a clear approval trail for regulated or high-risk content, reduces email-based sign-off, and ensures only signed-off assets are distributed to agencies, distributors, or retail partners.

2. Contract and Agreement Storage Linked to Approved Supporting Assets

Flow: OpenText Core Signature to Acquia DAM

After a contract, licensing agreement, or partner agreement is signed in OpenText Core Signature, the executed document can be automatically linked to related brand assets in Acquia DAM, such as logos, product images, campaign kits, or co-branded templates. This gives legal, marketing, and partner teams a single reference point for the signed agreement and the approved materials it governs.

Business value: Improves governance for partner marketing, licensing, and co-branding programs by connecting signed legal documents with the exact assets they authorize.

3. External Partner Onboarding with Signed Brand Usage Terms

Flow: Acquia DAM to OpenText Core Signature and back to Acquia DAM

When agencies, distributors, or franchisees request access to brand assets in Acquia DAM, they can first complete a usage agreement or brand compliance acknowledgment in OpenText Core Signature. After signature completion, access to the relevant DAM portal, collections, or download permissions can be granted automatically.

Business value: Ensures external users accept brand usage terms before receiving assets, reducing legal exposure and improving control over who can use which materials.

4. HR and Internal Policy Acknowledgment with Branded Documents

Flow: Acquia DAM to OpenText Core Signature

HR teams can store approved policy templates, onboarding documents, employee handbooks, and training collateral in Acquia DAM. These documents can then be sent to OpenText Core Signature for employee acknowledgment and signature. Signed copies can be archived alongside the source documents in Acquia DAM for easy retrieval.

Business value: Standardizes employee communications, speeds onboarding, and provides a controlled repository for signed policy documents and supporting materials.

5. Sales Enablement Content Approval for Customer-Facing Proposals

Flow: Acquia DAM to OpenText Core Signature

Sales and marketing teams can use Acquia DAM to manage approved proposal templates, product sheets, and customer-facing presentations. When a proposal or statement of work requires formal approval, the document can be routed through OpenText Core Signature before being shared with the customer or archived in the DAM as the final approved version.

Business value: Reduces version confusion, shortens approval cycles, and ensures customer-facing materials are both brand-approved and legally executed.

6. Compliance-Driven Approval of Regulated Marketing Content

Flow: Bi-directional

In regulated industries such as healthcare, financial services, or consumer goods, marketing content often requires both brand review and legal sign-off. Acquia DAM can manage the asset lifecycle and approval status, while OpenText Core Signature can capture formal legal approval for claims, disclosures, or regulated copy. The signed approval record can then be attached to the asset in Acquia DAM.

Business value: Provides a defensible audit trail for regulated content, reduces compliance risk, and makes it easier to prove which version was approved and by whom.

7. Distributor and Retail Partner Program Agreements Tied to Asset Access

Flow: OpenText Core Signature to Acquia DAM

Before distributors or retail partners gain access to seasonal campaign kits, product launch assets, or localized marketing materials in Acquia DAM, they can sign participation agreements in OpenText Core Signature. Once completed, the DAM can automatically provision access to the correct portal or asset collection based on the signed agreement.

Business value: Aligns asset distribution with contractual permissions, supports channel governance, and helps ensure partners only access materials they are authorized to use.

8. Audit-Ready Archive of Signed Documents and Related Assets

Flow: OpenText Core Signature to Acquia DAM

Organizations can use OpenText Core Signature to execute documents such as release forms, approvals, or agreements, then store the signed PDF, signature certificate, and related supporting assets in Acquia DAM. This creates a centralized archive where legal, marketing, and operations teams can quickly retrieve both the signed record and the associated creative materials.

Business value: Improves audit readiness, simplifies document retrieval, and reduces the risk of losing the context around signed approvals and the assets they support.