The Certificate of Completion (CoC) is a system-generated document that confirms the successful completion of a signing process. It is automatically created once all required signers have finished signing and is stored alongside the final signed document in Salesforce.
The CoC provides a verifiable audit record for legal, regulatory, and compliance purposes.
Why the Certificate of Completion Exists
Compliance, audit, and legal verification requirements often extend beyond the signed document itself. Organizations must retain a formal record that confirms how and when each required signing action was completed.
The Certificate of Completion addresses this requirement by providing:
A legally recognized record confirming document execution
Traceability for signer identity, authentication method, and signing timestamps
A consistent audit artifact stored directly in Salesforce alongside the signed document
This supports operational, legal, and regulatory review without reliance on external records or manual verification.
Salesforce Behavior
When the final signed document is pushed to Salesforce:
Merge mode: A single file is saved containing both the signed document and the Certificate of Completion.
Standalone mode: The signed document and the Certificate of Completion are saved as separate files.
Storage location:
The Certificate of Completion is stored in the same Salesforce location as the signed document, based on the trigger record configuration.
Use Cases
Compliance and audit: Legal teams require proof that all parties signed an agreement.
External verification: Customers request confirmation that all signers completed the agreement.
Regulated industries: Healthcare and financial services require documented consent trails.
Multi-party agreements: A single certificate captures signing activity across multiple participants.
Edge Cases and Special Behavior
Signer Types
CC recipients: Not included in the certificate
Reviewers: Displayed in the same format as signers
Salesforce signer: Displays as Unknown unless authenticated using an SSO session
Missing Signer Details
If either the first or last name is missing, the available value is shown
If both are missing, the name field is left blank
Signature Handling
If multiple signatures exist, the first signature is used
If no signature exists, initials are used
If neither exists, the field is left blank
All signature methods are supported: Type, Draw, Upload, Select
Signing Source
Sign from Web: Uses signer details defined in the Sign project
Sign and Send (Salesforce button): Uses Salesforce trigger user metadata
Titan Flow Behavior
Merge mode: The Certificate of Completion is included in the final document passed into Flow.
Standalone mode: The Certificate of Completion cannot currently be passed into Flow.
Feature Notes
The following behaviors are expected when using the Certificate of Completion:
Titan Flow support Standalone Certificates of Completion are not currently passed into Titan Flow.
Salesforce signer identification Salesforce signers appear as Unknown unless authenticated via an SSO session.
Multiple signatures Only the first signature is captured when multiple signatures exist.
Standalone file naming Standalone Certificates of Completion are saved in Salesforce under the document title “Certificate of Completion”.
