Documents & Contracts

Add the additional security options available for client documents to the Documents & Contracts page

The recent update to the Documents section has been a significant step backward in terms of usability and visibility. What was previously easy to navigate and largely accessible at a glance now requires multiple additional clicks to access basic information. Document Status Is No Longer Visible at a Glance Previously, we could quickly see whether a contract had been viewed and/or signed without having to navigate anywhere else. Now, we have to right-click the document, select "Details," wait for a popup, review the information, and then close the popup. This is unnecessary extra navigation for information that was readily visible before. Please restore the ability to see document activity and signing status directly within the Documents view. Client Portal Sharing Status Is No Longer Visible We can no longer quickly identify which files have been shared on the Client Portal. The only way to determine this now is to right-click a document and look for the "Stop Sharing" option, which is the only indicator that a file is being shared. This is another unnecessary step that makes managing client documents much less efficient. Sharing status should be clearly indicated in the Documents view, just as it was previously. Accidental Document Downloads Are a MAJOR Security Concern It is far too easy for a user to accidentally double-click certain file types (ex: HEIC) and trigger a download. In an environment where we handle protected health information (PHI), this creates a serious data security and compliance concern. Downloaded files are being saved to individual users' folders, outside of the centralized CRM environment. This creates unnecessary exposure and makes it much more difficult for administrators to maintain appropriate oversight of sensitive client documents. I strongly recommend the following functionality: Give administrators the ability to disable document downloads for users, allowing documents to be previewed within the CRM without the ability to download them. At a minimum, implement a confirmation popup before downloading a document, warning the user that the file will be saved locally and asking them to confirm that they wish to proceed. Overall Recommendation Please consider restoring the at-a-glance visibility of document statuses and sharing indicators, while also introducing administrative controls over document downloads.

Currently, while merge fields allow us to personalize the content of documents with contact-specific information collected from form responses, there is no built-in option to dynamically include such details—like first and last name—in the document name or title when the document is generated. This limitation makes it challenging to efficiently organize, search, and identify documents, especially when managing large volumes for multiple contacts. The ability to automatically populate the document name with unique contact information would greatly streamline our workflow and improve document management. ---- For example, if the contact fills out a "discovery" form with name and other discovery questions. Their form responses are mapped as contact fields and updated in the document, but I'd like the document name to also be updated with "Discovery {{contact.first_name}} {{contact.last_name}} "

I have numerous document templates I require of my clients but depending on the client/situation they may get some, or all, of them. I would like to be able to load several document templates into my editor at once based on the individual needs of the client, prepare them for signature at the same time, and send them out all together in one continuous scrolling file for them to sign instead of separate actions/emails.

GoHighLevel’s Documents & Contracts feature is a huge step in the right direction, but for users in financial services, insurance, and other regulated industries, it currently falls short of platforms like DocuSign in terms of compliance, auditability, and legal defensibility. I’d like to see GHL evolve its e-signature functionality into a compliance-grade solution that can fully replace third-party tools in high-trust environments. ⸻ Key Features Requested: Advanced Audit Trail (Court-Defensible) * Full event history (viewed, opened, signed, IP address, timestamps) * Tamper-proof certificate of completion * Downloadable audit log for legal use Identity Verification Options * SMS / email OTP verification * ID-based verification (driver’s license/passport) * Optional knowledge-based authentication (KBA) Compliance Certifications & Standards * SOC 2 Type II compliance * ESIGN + UETA clearly documented (U.S.) * GDPR / international compliance options * Clear security documentation for regulated industries Document Integrity & Encryption * End-to-end encryption * Document hashing to prevent tampering * Version control with locked final copies Role-Based Signing & Permissions * Multiple signer roles (client, advisor, witness, etc.) * Signing order enforcement * Conditional logic (only show fields to specific signers) Legal-Grade Storage & Retention * Secure long-term storage * Audit-ready retrieval * Retention policy settings ⸻ Why This Matters: Many GHL users (especially in financial services, real estate, legal, and insurance) currently rely on tools like DocuSign purely for compliance reasons—not because of workflow or usability. If GoHighLevel can match that level of security, verification, and auditability, it would: * Eliminate the need for external e-sign tools * Increase platform stickiness * Open the door to more regulated industries * Position GHL as a true all-in-one business OS ⸻ Ideal Outcome: A “Compliance Mode” or “Enterprise E-Sign Upgrade” that users can enable when needed, even as a paid add-on.

My clients submit real estate deals for funding and contracts are created/autofilled using opportunity data (property address, funding amount, title company, etc) rather than contact data. I'm having an issue where a contract is sent out for signing and if the same contact submits another property, the data from the first property is being overwritten by the second property. I had to create custom contact fields because I cant use custom opportunity fields within the contract, so GHL thinks the contact data is just being updated rather than it being a completely separate opportunity.

Description: Currently, GoHighLevel does not provide the ability to rename documents once they've been uploaded. Files retain their original file names, which can be problematic when managing multiple documents. It becomes time-consuming to open each file individually to identify its contents. Request: We would greatly benefit from the ability to rename files directly within GoHighLevel after they have been uploaded. This feature would save time, improve document organization, and enhance overall user experience, particularly for teams managing high volumes of files. We hope this feature can be considered for future updates. Thank you!

In GHL Facebook Meta conversion API module currently only FBCLID event option is available. Need other parameters to be added as well. Like its available in zapier and MAKE facebook conversion API module. Paramters missing IN GHL = em: Email — Hashing required ph: Phone Number — Hashing required fn: First Name — Hashing required ln: Last Name — Hashing required ge: Gender — Hashing required db: Date of Birth — Hashing required ct: City — Hashing required st: State — Hashing required zp: Zip Code — Hashing required country: Country — Hashing required external_id: External ID — Hashing recommended client_ip_address: Client IP Address — Do not hash client_user_agent: Client User Agent — Do not hash fbc: Click ID — Do not hash fbp: Browser ID — Do not hash subscription_id: Subscription ID — Do not hash fb_login_id: Facebook Login ID — Do not hash lead_id: Lead ID — Do not hash anon_id: Install ID — Do not hash (Note: This parameter is for app events only) madid: Mobile Advertiser ID — Do not hash (Note: This parameter is for app events only) page_id: Page ID — Do not hash page_scoped_user_id: Page scoped user ID — Do not hash ctwa_clid: Click to WhatsApp ID — Do not hash ig_account_id: IG account ID — Do not hash ig_sid: Click to Instagram ID — Do not hash

There is only one size available for text fields in contracts. This makes working with existing fill in the blank contracts ( uploaded as PDFs ) extremely difficult. I don't control the size of the fill in the blank forms and with the default font size, the text often runs onto the next line, making the whole PDF difficult to read. Lack of being able to size the text appropriately to fit the provided blank sizes makes working with PDFs contracts in high level extremely difficult. I'm a real estate agent. We have to use existing PDFs for contracts and leases. I'm sure there are other industries with similar requirements. Contracts in High Level are so close to being use-able but they're not quite there yet.

It would be really nice if we added some PandaDoc features. PandaDoc allows us to put in pre-saved sections, so that way we can have essentially one master contract. We can fill in sections of the contract according to what services clients sign up for.