Use Private Contact Notes Without Exposing Them to Signers

Use the Notes field on a QCDS Contact for sender-side reference information about that reusable Contact. Current QCDS keeps Contact Notes out of the participant snapshot and does not use them as signer-page, email, or completed-document content.

Add or Edit Contact Notes

  1. Open Contacts in the QCDS frontend workspace.
  2. Add a Contact or edit an existing Contact.
  3. Enter the internal reference text you need in Notes.
  4. Click Save Contact.

The Notes field is multiline and stored with the Contact. It is useful for sender-side context such as relationship details, handling reminders, or other operational information that does not belong in the signing transaction.

Why Signers Do Not See Contact Notes

When a saved Contact is assigned to a Request, QCDS copies only the participant information needed by the signing workflow—such as identity/name, email addresses, primary phone/address, company, title, language, locale, and time zone. Contact Notes are not copied into that participant snapshot.

The current email-delivery and signer-page paths likewise do not treat Contact Notes as message content or signer-visible profile data. They are not inserted into the completed PDF simply because they exist on the Contact.

Keep the Privacy Boundary Clear

Private in this context means not exposed through the normal signer workflow; it does not mean the Notes field is a password vault or secret-management system. Authorized users who can manage the workspace's Contacts can view the Contact record, and protected workspace export functions can include sensitive Contact data when that export scope permits it.

Good Uses for Notes

  • Internal relationship or account context.
  • Operational reminders for senders who work with that Contact.
  • Information that helps identify the correct Contact but should not become part of a Request.

Do Not Put These in Notes

  • Passwords, API secrets, recovery codes, or identity-provider credentials.
  • Text that must become part of the signed agreement; place that content in the actual document or supported Request fields instead.
  • Instructions the signer must receive; use the appropriate Request/email content for participant communication.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDS feature? Visit the QC Digital Signature Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.