Company
Glossary
Digital trust has its own language. This glossary explains it in plain words — from qualified signatures and verified identity to content provenance. Search for a term, or browse the full list from A to Z.
A
Active approver
A participant who must explicitly approve something before the workflow can continue. This role is stronger than being copied, notified, or allowed to observe, because the process depends on their action. If the active approver rejects, ignores, or delays the request, the workflow may stop, reroute, or escalate.
Advisory vote
A vote that gives structured input into a decision without necessarily deciding the legally binding outcome by itself. It is useful when a group’s opinion should be recorded, but final authority remains with another person, body, or rule. Advisory votes can still be important evidence because they show who supported or opposed a proposed decision.
AI
Artificial intelligence. Netlock’s AI can analyse documents, detect patterns, assist workflows, classify information, or generate synthetic media such as images, audio, video, or text.
AI Act
The European Union regulation creating harmonised rules for artificial intelligence. It uses a risk-based approach, with different obligations depending on whether an AI system is prohibited, high-risk, limited-risk, or lower-risk.
AML
Anti-Money Laundering — checks, controls, and reporting processes designed to reduce the risk that financial systems are used to hide criminal funds. In digital identity and signing workflows, AML often connects to identity verification, sanctions screening, beneficial ownership checks, and audit evidence.
AMLR
The EU Anti-Money Laundering Regulation, part of the EU’s move toward a more unified anti-money-laundering rulebook across Member States. In high-assurance identity and financial workflows, AMLR is relevant because regulated organisations may need stronger evidence about who acted, who owns an entity, and how checks were performed.
Anti-spoofing
Technology that tries to stop fake identity attacks during verification. In biometric checks, this may include detecting masks, replayed videos, printed photos, deepfakes, or manipulated images. It is closely related to presentation attack detection, which NIST and ISO describe as detecting attempts to fool a biometric capture system.
API
Application Programming Interface — a structured way for one software system to communicate with another, usually through defined requests, responses, and permissions. In workflow platforms, APIs allow signing, identity, storage, billing, CRM, or compliance systems to connect without users manually copying data between tools.
API key
A credential used by software to access an API. It works like a machine-to-machine identity, helping the receiving system recognise which application is making the request. Because it can grant access to sensitive functions, it should be protected, rotated when needed, and limited to the smallest practical permissions.
Audit trail
A record of what happened, who did it, when it happened, and sometimes why it happened. It helps prove the history of actions inside a system, especially during approvals, signing, access, decryption, or compliance review. A strong audit trail is useful because it turns a workflow from a simple sequence of clicks into defensible evidence.
B
Batch signing
Signing multiple documents in one action instead of repeating the same signing process document by document. It is useful when the same signer must approve many similar files, such as HR documents, invoices, certificates, or internal approvals. The system still needs to preserve evidence for each document, even if the user experience feels like one combined action.
Browser-based editor
An editor that runs inside a web browser instead of requiring a separate desktop application. It can make document editing easier for distributed teams because users can work from managed links and controlled permissions. In trust workflows, the editor should preserve version history and avoid creating uncontrolled local copies.
C
C2PA
The Coalition for Content Provenance and Authenticity — an open technical standard for attaching provenance information to digital content, helping users understand the origin and editing history of media. This is especially relevant for AI-generated or edited images, audio, video, and other digital assets where authenticity is hard to judge visually.
CC recipient
A participant who receives a copy of a workflow communication or document but is not necessarily an approver or signer. They are included for awareness, transparency, or coordination. A CC role should not be confused with an active approval role, because the workflow normally does not wait for their decision.
CLM
Contract Lifecycle Management — the full process of managing contracts, from drafting and negotiation to approval, signing, storage, obligations, renewals, and follow-up. In a digital trust environment, CLM often connects document control, identity, approvals, version history, and evidence packages.
Compliance
Following legal, regulatory, contractual, and internal policy requirements in a documented and defensible way. It is not only about obeying rules, but also being able to prove that the right process was followed. In workflow systems, compliance is supported by permissions, audit trails, templates, approval rules, retention, and reporting.
Content authenticity
The ability to show that content came from a known source and that its history or integrity can be checked. It does not always mean the content is “true,” but it can help show whether it was created, edited, approved, or published through trusted steps. Standards such as C2PA are designed to support this kind of content transparency.
Content credentials
Information attached to content that helps explain where it came from, how it was handled, and what trust signals are linked to it. They may include provenance details, creator or publisher information, editing history, and technical verification data. Their value is that a viewer can inspect trust information instead of relying only on appearance.
Content hash
A mathematical fingerprint of a file. If the file changes, even slightly, the hash usually changes too. This makes hashes useful for detecting tampering, matching files, and proving that a specific document is the same one that was approved or signed.
Content library
A managed repository for important files, records, templates, or media assets. It is designed to make retrieval, reuse, permission control, and verification easier. In governance workflows, it can help teams avoid using outdated files or unofficial versions.
Counterparty
The other person or organisation involved in an agreement, negotiation, transaction, or workflow. In a contract, for example, the counterparty may be the customer, supplier, partner, or institution on the other side. Identifying the counterparty correctly is important for authority checks, risk scoring, sanctions screening, and signing rights.
Credit-per-action pricing
A model where usage costs are tied to actual actions rather than mainly to user accounts. A credit might be consumed by a signature, verification, upload, approval, document generation, or API transaction. This model can be attractive when occasional users need access, but the organisation wants costs to reflect real activity.
Cryptographic proof
Evidence created with cryptographic methods that helps show a file, identity, signature, timestamp, or action can be trusted and checked later. It may involve hashes, digital signatures, certificates, timestamps, or protected logs. Its purpose is to make trust verifiable rather than dependent only on screenshots or manual statements.
Cryptographic provenance record
A history of origin and changes protected by cryptographic methods. It can help prove that the record has not been silently altered and that important events are linked to trusted sources. In content authenticity, this can support later verification of who created, edited, approved, or published an asset.
Cryptographic redaction
Protecting hidden document content with cryptographic controls rather than simple visual masking. This is stronger than placing a black box over text, because the hidden data can be encrypted and access-controlled. It can also allow authorised users to verify that redacted information exists without exposing it to everyone.
D
DAC7
An EU tax-transparency framework relevant to digital platforms and online sellers. It introduced reporting obligations for certain platform operators so tax authorities can receive information about relevant seller activities. In trust and identity workflows, it can matter where platforms need reliable seller identification and defensible reporting records.
Data sovereignty
Control over where data is stored, who governs it, and which legal or geographic rules apply to it. It is especially important when sensitive business, identity, health, financial, or government-related information crosses borders. In practical terms, it can influence hosting location, cloud provider choice, access controls, encryption, and contractual obligations.
Deadlock detection
A workflow feature that identifies process designs where progress becomes impossible because of conflicting dependencies. For example, one approval might depend on another approval that can never happen under the current rules. Detecting deadlocks early helps avoid workflows that look valid on paper but cannot reach completion.
Decryption
The process of turning encrypted information back into readable information for an authorised user or system. It requires the correct key, permission, or cryptographic process. In document workflows, decryption should usually be logged because it may expose sensitive information.
Decryption audit trail
A record of who decrypted protected data, when they did it, and under what circumstances. It may also record the document, field, reason, device, IP address, or authorisation path. This is important because access to hidden or encrypted content is often more sensitive than ordinary document viewing.
Deepfake
Synthetic or manipulated audio, video, or image content designed to look or sound convincingly real. It can be used for entertainment, accessibility, or creative work, but also for fraud, impersonation, misinformation, or identity attacks. This is why provenance, liveness checks, and content credentials are increasingly important in trust systems.
Digital identity
A verified digital representation of a person, organisation, or sometimes a device. It can be used for login, signing, approval, age or eligibility checks, and other trusted actions. Modern digital identity guidance covers identity proofing, authentication, and federation across systems.
Digital Product Passport
A digital record framework linked to product traceability, sustainability, durability, and environmental information in the EU regulatory environment. It is intended to store and share relevant product data with consumers, businesses, and public authorities. It matters for provenance because it connects products to structured, verifiable lifecycle information.
Document authentication
Checking whether an identity document or supporting file appears genuine and untampered. It can include checking visible security features, metadata, issuing patterns, document numbers, fonts, images, and consistency with known formats. In high-assurance workflows, it is often combined with face matching, liveness checks, and audit evidence.
Document classification
The process of identifying what type of document something is. This can be done manually or automatically using rules, metadata, templates, or AI-based recognition. Classification matters because different document types may require different retention periods, approvals, redactions, signatures, or compliance checks.
Document fingerprinting
Creating a technical signature of a file so later versions or altered copies can be matched back to it. Unlike a simple filename, a fingerprint is based on the content or structure of the document. It is useful for detecting duplicates, proving integrity, and connecting redistributed files to an original trusted record.
DOCX
The standard Microsoft Word format for editable text documents. It is useful during drafting and collaboration because the content remains structured and editable. In controlled workflows, a DOCX may later be converted into a PDF or signed format once the text is final.
DORA
The EU Digital Operational Resilience Act. It applies to financial-sector entities and certain ICT third-party providers, focusing on the ability to withstand, respond to, and recover from technology disruptions such as cyberattacks or system failures. In digital trust workflows, it matters because financial organisations may need strong operational controls, incident records, vendor governance, and resilience evidence.
Dynamic workflow logic
Workflow rules that change behaviour based on conditions. These conditions can include document type, transaction value, department, risk score, signer location, participant role, or previous decisions. This allows one workflow template to handle many real-life scenarios without manually rebuilding the process each time.
E
eFTI
Electronic Freight Transport Information — the EU framework allowing economic operators to share regulatory freight transport information electronically with competent authorities. In logistics workflows, it matters because transport records need to be structured, accessible, and trusted across road, rail, inland waterway, and air transport contexts.
eIDAS
The EU regulation for electronic identification and trust services. It provides a legal framework for electronic signatures, seals, timestamps, electronic identification, and related trust services across the EU. In digital signing workflows, eIDAS is central because it defines recognised levels of trust and the role of qualified trust service providers.
Encryption
A method of protecting information so that only authorised parties can read it. It transforms readable data into protected data using cryptographic methods and keys. In document workflows, encryption can protect entire files, specific fields, storage locations, or data moving between systems.
Encryption key
The secret value used by an encryption system to lock or unlock protected data. Whoever controls the key may control access to the protected information, so key management is critical. Good systems limit key exposure, rotate keys when appropriate, and use secure storage such as hardware security modules for sensitive operations.
Enterprise hierarchy
A structured model of departments, subsidiaries, teams, roles, or related legal entities inside a larger organisation. It helps a workflow understand reporting lines, approval rights, escalation paths, and policy boundaries. In complex organisations, hierarchy prevents every process from needing to be manually configured from scratch.
Evidence package
A bundled set of records that helps prove a process was carried out correctly. It may include identity checks, timestamps, approvals, signatures, document hashes, version history, certificates, IP addresses, and supporting files. The purpose is to make later review, audit, dispute handling, or legal validation easier.
F
Face matching
Technology that compares a live face image or selfie with the face shown on an identity document or trusted reference. It helps confirm that the person presenting the document is likely the same person shown in the document. For stronger assurance, it is usually combined with liveness detection and document authentication.
Field-level encryption
Protecting specific pieces of data inside a document, form, or database instead of encrypting only the whole file. For example, a salary, ID number, bank account, or medical field could be encrypted separately. This allows the wider document to remain usable while sensitive fields stay protected.
Fingerprint-based verification
Reconnecting altered or redistributed files to an original trusted record using technical file fingerprints or similarity matching. It can use exact cryptographic hashes or more flexible similarity techniques, depending on the use case. This is useful when files may have been renamed, compressed, converted, or slightly modified.
G
GDPR
The EU General Data Protection Regulation. It protects natural persons when their personal data is processed by private-sector organisations and most public-sector bodies. In workflow systems, GDPR matters because identity data, signatures, IP addresses, audit logs, and document contents may all contain personal data.
Graph-based execution engine
An engine that models workflow actions and dependencies as a network rather than a simple straight line. This makes it easier to handle parallel approvals, conditional paths, fallback routes, voting rules, and complex dependencies. It is especially useful when a workflow has many participants and the next step depends on several previous outcomes.
H
HMAC
Hash-based Message Authentication Code — a cryptographic method used to check that a message came from someone with the expected secret key and that the message was not altered in transit. HMAC is commonly used in APIs, webhook verification, and system-to-system authentication.
HSM
Hardware Security Module — a specialised device or appliance used to protect cryptographic keys and perform sensitive cryptographic operations in a controlled environment. HSMs are often used when signing keys, certificate keys, or high-value encryption keys must be strongly protected.
I
Identity federation
A way of linking identity systems so users can authenticate through an existing trusted provider. It allows a relying application to accept identity information or assertions from another system instead of managing every credential directly. NIST digital identity guidance treats federation as a core part of modern identity architecture.
Immutable
Designed so that it cannot be silently changed without detection. In digital trust, it often means tamper-evident rather than physically impossible to alter. The goal is that any unauthorised change becomes visible through logs, hashes, signatures, version history, or other verification methods.
Impossible-outcome detection
Logic that identifies workflow states where the required result can no longer be achieved. For example, if a voting rule requires five approvals but too many voters have already rejected, the workflow may know the proposal cannot pass. Detecting this early saves time and allows the process to close, escalate, or restart.
IP address
A network address that identifies the connection point of a device on the internet or another IP-based network. In audit trails, it can help show where a login, approval, signature, or access event appeared to come from. It should be treated carefully because it can be personal data and may not always identify a person with certainty.
K
Key rotation
The controlled replacement of cryptographic keys over time. It reduces risk if an old key is exposed, overused, or no longer meets security requirements. In well-managed systems, rotation is planned so protected data and integrations continue to work while trust is maintained.
KYB
Know Your Business — a process for verifying an organisation, including its registration details, ownership, authority structure, and sometimes its business activities. KYB is important where a company needs to prove that a counterparty is legitimate and that the person acting for it has authority.
KYC
Know Your Customer — a process for verifying the identity of a person before allowing trusted, regulated, or higher-risk actions. KYC can include document checks, biometric checks, address checks, sanctions screening, and risk-based due diligence.
L
LDAP
Lightweight Directory Access Protocol — a directory technology often used in enterprise identity and access systems. In practice, LDAP can help applications look up users, groups, departments, and permissions from a central directory.
Liveness detection
A check used during identity verification to assess whether the person being scanned is physically present. It helps reduce the risk of attacks using photos, screens, masks, recorded videos, or other presentation attacks. In biometric standards and guidance, this is closely related to presentation attack detection.
Lot number
An identifier that connects a product unit or batch to manufacturing and traceability records. It can help identify when and where a product was made, which materials or processes were used, and which other units belong to the same batch. In compliance or recall scenarios, lot numbers make it easier to find affected products.
M
Metadata
Data about data. For a file, it can include origin, author, creation date, edit history, rights information, document type, verification status, or technical properties. Metadata is useful for search, governance, provenance, and automated workflow decisions.
MFA
Multi-Factor Authentication — requiring more than one type of proof, such as a password plus a code, device confirmation, biometric factor, or security key. MFA reduces the risk that one stolen credential is enough to access an account or approve a sensitive action.
Moderation evidence
The records and linked facts that help show why a platform took a moderation or enforcement action. It may include the reported content, policy rule, reviewer notes, timestamps, user history, automated detection results, and appeal information. This evidence matters because platforms may need to justify decisions to users, auditors, regulators, or courts.
N
NDA
Non-Disclosure Agreement — a legal agreement used to protect confidential information from being shared or used improperly. In workflow systems, NDAs often need careful version control, counterparty identification, signing evidence, and storage for later reference.
Neural fingerprinting
A content-matching technique that uses machine-learning methods to recognise related files even after transformation. It can help identify images, videos, audio, or documents that are visually or semantically similar even if they are not identical at the byte level. This is useful when content has been resized, cropped, compressed, edited, or republished.
NIS2
The EU Network and Information Security Directive 2. It raises cybersecurity and incident-management expectations for in-scope sectors and organisations. In trust workflows, NIS2 can matter because organisations may need stronger security governance, supplier controls, incident reporting, and resilience evidence.
O
OIDC
OpenID Connect — an interoperable authentication protocol built on OAuth 2.0, widely used for login and single sign-on. In workflow platforms, OIDC can allow users to authenticate through an existing identity provider instead of creating separate local passwords.
On-premises
Software or storage deployed inside the customer’s own infrastructure rather than fully hosted by an outside cloud provider. It can give an organisation more direct control over hosting, network access, data location, and integration with internal systems. It may also require more internal responsibility for maintenance, security updates, backups, and resilience.
P
PAdES Baseline LTA
A long-term PDF electronic-signature profile designed to remain verifiable for many years. ETSI describes PAdES baseline levels as adding requirements for preserving signature validity over the long term. LTA is relevant when signed PDFs may need to be validated long after certificates, timestamp material, or revocation data have changed.
Passive approver
A participant who may intervene within a defined time window but does not block the workflow by default. If they do nothing, the workflow may continue automatically after the waiting period. This is useful for review models where silence means no objection, but the participant still has a chance to stop or comment.
Portable Document Format — a widely used file format for fixed-layout digital documents, especially when the appearance of the document should remain stable across devices. In signing workflows, PDF is common because it supports visible signature fields, embedded signature data, and long-term validation profiles.
Perceptual hashing
A method for matching files that look or sound similar even if they are not bit-for-bit identical. It is different from a cryptographic hash, which usually changes completely after even a tiny file modification. Perceptual hashing is useful for detecting resized, compressed, cropped, or slightly edited media.
Policy injection
Automatically adding required participants, steps, or rules into a workflow based on organisational policy. For example, legal review might be inserted for high-value contracts, or finance approval might be inserted for payment-related documents. This helps enforce governance without relying on every user to remember every rule.
Presigned upload
An upload method where a temporary secure link allows a file to be sent directly to storage. It limits exposure because the uploader does not need broad storage credentials. This is often used to make uploads faster and safer while keeping access time-limited and purpose-specific.
Private version
A document version where all data remains visible, but access is restricted to authorised users. It is useful when the complete document must be preserved for legal, operational, or audit reasons. The key difference from a protected or redacted version is that the content is not necessarily hidden inside the file, but the file is access-controlled.
Protected version
A privacy-safe document version in which sensitive fields are hidden and encrypted while the file remains usable. It allows broader sharing of a document without exposing all underlying data. In stronger implementations, authorised users may later reveal or verify protected fields through controlled access.
Provenance
The origin and history of a file, record, or asset. It can show where something came from, who handled it, what changes were made, and which approvals or signatures are linked to it. In digital content, provenance is becoming more important because AI and editing tools make visual authenticity harder to judge.
Proxy voting
A governance method where one authorised participant votes on behalf of another. The authority to vote should be clearly granted, limited, and recorded. In digital workflows, proxy voting needs evidence showing who delegated the vote, who cast it, and whether the proxy acted within scope.
PSD2
The revised EU Payment Services Directive. It promotes secure and innovative payment services and introduced strong customer authentication requirements for many electronic payment contexts. In identity workflows, PSD2 is relevant because it made stronger authentication and fraud reduction central to digital payments.
Pseudonymous certificate
A certificate that lets a user participate in a process without exposing ordinary identity details to every participant. It can still support trust because the certificate is issued and controlled through a defined identity or trust process. This is useful when a person’s authority or eligibility must be proven, but their full identity should not be visible to all parties.
Public verification
A way for outside parties to check whether a file, trust record, signature, approval, or provenance claim is authentic. It should not require the verifier to have internal system access beyond what is intentionally exposed. Public verification is useful for certificates, signed documents, official publications, trusted media, and compliance evidence.
Q
Q&A
Question and answer. In document systems, it often means asking natural-language questions over stored records, contracts, policies, or evidence packages. It can help users retrieve information faster, but the system should still preserve source links and context so answers can be checked.
QES
Qualified Electronic Signature — under eIDAS, a high-assurance type of electronic signature linked to qualified trust services and specific legal requirements. It is often used where strong identity assurance and cross-border legal recognition are important.
QTSP
Qualified Trust Service Provider — an organisation supervised to provide qualified trust services under the eIDAS framework, such as qualified signatures, seals, timestamps, or related validation services. QTSPs matter because qualified trust services rely on regulated providers and trusted lists.
Qualified digital identity
A digitally usable identity created through a high-assurance trust process and intended for later trusted actions. It may be used to support qualified signatures, regulated onboarding, or other legally sensitive workflows. The key idea is that the identity is not just a casual account, but a verified identity suitable for stronger reliance.
Qualified electronic seal
A trust-service mechanism similar to a signature, but usually used by a legal person or organisation rather than an individual person. It helps prove the origin and integrity of an organisational document or data object. Under eIDAS, qualified trust services must meet specific requirements and be recognised across Member States.
Qualified timestamp
A regulated timestamp proving when something existed or when an action occurred at a particular moment. It is useful for signatures, audit evidence, submissions, records, and long-term validation. In trust workflows, timestamps help show not only what happened, but when it happened according to a trusted time source.
R
Redacted version
A document version where some information has been hidden because it is sensitive or should not be shared widely. Redaction can protect personal data, trade secrets, financial details, or investigation information. Strong redaction should remove or cryptographically protect hidden content, not merely cover it visually.
Replay attack
Fraudulent reuse of previously captured valid data to fool a system. For example, an attacker might resend an authentication message, video, token, or signed request to make it appear current. NIST describes replay attacks as reusing captured messages to impersonate a legitimate claimant or verifier.
Replay prevention
Technical controls designed to stop replay attacks. Common methods include nonces, timestamps, session binding, challenge-response checks, and one-time tokens. The goal is to make sure a request or identity signal cannot simply be copied and reused later.
Rights documentation
Contracts, licences, releases, assignments, consents, or other records that show who may use content and under what conditions. It is especially important for media, brand assets, AI training data, creative work, and user-generated content. Good rights documentation helps prove permission, scope, duration, territory, and restrictions.
Risk scoring
A way of assigning more or less risk to a document, clause, identity, action, counterparty, or event. The score may be based on rules, data signals, history, AI analysis, or compliance requirements. It helps teams focus attention on items that need stronger review, step-up authentication, escalation, or manual approval.
S
SAML
Security Assertion Markup Language — an XML-based standard for exchanging security information between identity providers and service providers, commonly used for enterprise single sign-on and identity federation. In workflow systems, SAML can let employees access tools through their organisation’s existing identity provider.
Sanctions screening
Checking whether a person, organisation, owner, or counterparty appears on a restricted or sanctioned-party list. It is often part of AML, KYC, KYB, export-control, or counterparty-risk processes. In digital workflows, sanctions screening should be logged so the organisation can prove when and how the check was performed.
Secret ballot
A voting method where individual votes are hidden from ordinary participants while the result remains valid and auditable. It protects voters from pressure, retaliation, or unnecessary exposure. A well-designed digital secret ballot should separate vote secrecy from proof that the process was legitimate.
Self-contained document
A document that carries enough of its own information or proof to remain useful without depending heavily on external systems. For example, it may include embedded signatures, timestamps, certificates, provenance data, or verification metadata. This helps preserve trust when a document is archived, forwarded, or checked years later.
Signature field
The specific place in a digital document where a signer is asked to apply a signature or approval. It can define who should sign, where the signature appears, and what part of the document is being accepted. In structured signing workflows, signature fields help prevent missed signatures and unclear signing responsibilities.
SIM swap
A telecom account change that moves a phone number to a different SIM card. It can be legitimate, such as when replacing a lost phone, but it is also a known fraud vector. Attackers may use SIM swaps to intercept SMS codes, reset accounts, or defeat weak forms of authentication.
SIU
Special Investigation Unit. In insurance, it usually refers to a team that investigates suspicious claims, fraud indicators, or unusual activity. In document and evidence workflows, an SIU may need controlled access to claim files, audit trails, identity records, and supporting evidence.
SME
Small and medium-sized enterprise — a business smaller than a large enterprise that may still have significant compliance, contracting, HR, finance, and identity needs. SMEs often benefit from templates, automation, and simple pricing because they may not have large legal or IT departments.
SOX
Sarbanes-Oxley — a US corporate-control and financial-reporting framework often referenced in compliance discussions. In workflow systems, SOX relevance usually appears around approval controls, audit trails, segregation of duties, and evidence that financial processes were properly followed.
SSO
Single Sign-On — letting users access multiple systems through one main identity provider instead of managing separate credentials for every application. In enterprises, SSO improves user experience and can centralise security controls such as MFA, access policies, and offboarding.
Step-up authentication
A stronger identity check triggered only for more sensitive actions. For example, a user may log in normally but need an extra factor before changing bank details, decrypting protected fields, or signing a high-value contract. This balances security and usability by applying extra friction only when risk is higher.
Structured review round
An organised review phase with clear participants, rules, deadlines, and version handling. It defines who reviews, what they can do, how comments are captured, and when the workflow can move forward. This avoids informal review chaos where feedback arrives in scattered emails, chat messages, or uncontrolled document copies.
T
Tamper-evident
Designed so that unauthorised change leaves detectable signs rather than remaining invisible. In digital systems, this can be achieved through hashes, signatures, logs, timestamps, or linked version records. It does not always prevent tampering, but it helps reveal that tampering happened.
Template
A reusable starting document or workflow pattern. It reduces repetitive setup work and helps ensure consistent wording, approvals, fields, and compliance steps. Templates are especially useful when many teams need to follow the same process without reinventing it each time.
Trusted file
A file that carries enough provenance, identity, signature, approval, or integrity evidence to be considered more reliable than an ordinary unverified file. It may include hashes, timestamps, audit trails, certificates, or content credentials. The trust comes not just from the file itself, but from the evidence connected to it.
U
UBO
Ultimate Beneficial Owner — the real person who ultimately owns or controls a business entity, even if ownership passes through other companies or legal structures. UBO checks are important in AML, KYB, sanctions screening, and counterparty-risk workflows.
UGS platform
As used here, a user-generated-content style environment where users upload media or documents that the platform must review and govern. Such platforms may need moderation evidence, provenance checks, rights documentation, and content authenticity signals. The term is especially relevant where large volumes of uploaded content create legal, reputational, or safety risk.
V
Version chain
The linked sequence of drafts, revisions, reviews, and approved versions that shows how a document or content asset evolved. It helps answer which version was reviewed, which version was signed, and what changed between stages. A reliable version chain reduces disputes caused by uncontrolled copies or unclear edits.
Version snapshot
A recorded state of a document or contract at a meaningful point in its lifecycle. It might be captured before review, after negotiation, at approval, at signature, or at publication. Snapshots make it possible to prove what the document looked like at a specific moment.
Video keyframe analysis
Comparing important frames in a video to help identify related, copied, or derived versions. Instead of analysing every single frame, the system focuses on representative frames that capture meaningful visual content. This can support moderation, provenance, copyright review, and detection of altered or republished videos.
W
Webhook
An automated message sent from one system to another when a specific event happens. For example, a signing platform might send a webhook when a document is signed, rejected, expired, or viewed. Webhooks are useful for integrations because they let systems react in near real time without constant manual checking.
Weighted voting
A voting method where some votes count more than others according to predefined rules. The weighting may reflect ownership share, department authority, legal role, seniority, or another governance structure. In workflow systems, the rules must be clear so the result can be calculated and audited correctly.
WOPI
Web Application Open Platform Interface — a Microsoft protocol used to integrate Microsoft 365 for the web with other applications and storage systems. In document workflows, WOPI can allow browser-based viewing and editing of Office documents while the host system keeps control of storage and permissions.
Workflow injection
Automatically reusing or inserting an existing workflow structure into a new process. For example, a policy might inject legal approval, finance approval, or compliance review when certain conditions are met. This helps apply governance consistently without requiring users to manually select every required step.
Tell Us What You Need to Prove
We’ll show you the fastest way to start, from one workflow to an organisation-wide proof layer.