Mobile-ID · Digital Trust
ISO/IEC 27001 · FIDO2 · OpenID — View scope
Mobile-ID SignGoPaperless Digital Signing
VIGet Started
SOLUTION · USE CASE

NDA

The CLM finalizes recipient, information scope and term, then checks each party’s signing authority.

ON THIS PAGE
CONCEPTUAL

Business implementation record

If the table is wider than its frame, scroll horizontally to see all columns; use arrow keys when the table region has focus.

Business implementation record
Control pointApplicable design
ActorsLegal reviewer and party representatives
TriggerFinalize parties, scope, term and signing authority
Source systemCLM / DMS
DocumentsNon-disclosure agreement and information scope
Approval controlFinalize parties, scope, term and signing authority
Identity and authorityMatch the participants, representation authority and document scope before requesting authorization.
Signing routeAPI or Agent connects an agreed VNeID/RS-HUB or Trusted SIC route; fallback requires an approved deployment policy.
Business exceptionsParty change; expiry; information scope unresolved
Downstream systemCLM / agreement repository
CONCEPTUAL

Responsibility from approval to handoff

  1. 01
    CLM / DMS

    The CLM finalizes recipient, information scope and term, then checks each party’s signing authority.

  2. 02
    Legal reviewer and party representatives

    Legal reviewer; information owner; representatives of both parties review the document and representation authority before authorizing signing.

  3. 03
    Mobile-ID Sign

    Correlate the signing request with nda and confidential-information scope and its approved version; retain the transaction reference.

  4. 04
    CA / RSSP

    The approved provider creates the signature using the applicable certificate and authorization; do not change routes without approval.

  5. 05
    CLM / agreement repository

    Retain NDA version, signers and approval reference; access to confidential information remains enterprise-controlled.

CONCEPTUAL

Record-specific exceptions and evidence

Exception handling

Party change; expiry; information scope unresolved.

The CLM / DMS owner decides whether to amend, cancel or request a new signature. Reconcile delayed callbacks against the original transaction before creating a replacement.

Handoff evidence

  • Non-disclosure agreement and information scope — Version and reference
  • Legal reviewer and party representatives — Roles and authority
  • Finalize parties, scope, term and signing authority — Decision and time
  • Signing — Authorization, route and verification result
  • CLM / agreement repository handoff — Acknowledgement and exceptions

This is a reference implementation workflow. The organization determines business policy, legal requirements and acceptance conditions.

RELATED

Related content

Choose the next document for your task.

ProcurementPurchase order, supply agreement and acceptance record. Review budget, supplier and purchasing authority; retain signing outcomes and evidence for the business handoff.Sales ContractFinal quotation, agreement and annexes. Approve terms, price and representation authority; retain signing outcomes and evidence for the business handoff.EnterpriseContracts, HR, procurement, internal documents and ERP/DMS systems can access digital signing through Agent or API.Industry SolutionsMap signing journeys, trust boundaries, evidence and integration patterns to industries with demanding legal and operational requirements.
NEXT STEPDiscuss deployment requirements

Search Mobile-ID Sign

Local search inside the offline package.