Skip to main content

Changelog

Follow new updates and improvements to Growably.

🚀Multi-role signing for your Documents and Contracts templates, right inside Workflows

Documents and Contracts templates can now carry multiple signer roles — buyer, seller, witness, or any custom role you define. When a document goes out through a Workflow, every role is automatically populated and routed for signature, no manual re-entry required.

🤔 The Challenge

You send agreements that need more than one signature — a buyer and a seller, a client and a co-signer, a tenant and a guarantor. Until now, templates only supported a single signer, so you were stuck manually adding each person’s details every time you sent a document, or working around it with clunky duplicate templates.

✨ Our Solution

Define signer roles directly on your template — up to 6 per template — and assign fields (like signature or date) to each one. When you send that template through a Workflow, HighLevel automatically pulls in the roles you’ve set up. Missing a detail? You can fill it in — or override any role’s name, email, or phone number — right at the workflow level, without touching the template.

🏆 How This Supercharges Your Business

  • Save Time: No more manually re-adding signer details for every multi-party agreement you send.

  • Reduce Errors: Role values set on the template auto-populate, cutting down on missed or mistyped signer info.

  • Stay Flexible: Override any role’s details per-workflow, so one template can serve many different deals.

  • Scale Complex Deals: Real estate, contracting, and services businesses can now route agreements needing multiple signatures (e.g., buyer + seller + witness) in a single send.

🛠️ How to Get Started

  1. Build your template: Open your Proposal/Estimate template and define signer roles (name, email, phone) and assign at least one fillable element to each role. Roles can have static or custom values which get resolved when the document is sent — choose based on your use case.

  2. Assign a Contact field: Make sure at least one fillable element is assigned to “Contact” — this is required for the Workflow send action to work.

  3. Select your template in a Workflow: Add the “Send Document” action and choose your multi-role template — roles will auto-populate.

  4. Override if needed: Adjust any role’s name, email, or phone at the workflow level — these values take precedence over the template defaults.

  5. Send: Launch the workflow — each signer receives their document in the order and role you’ve defined.

🔮 What’s Next?

We’re continuing to build out signing order controls and expanding role-based automation across more document types — so stay tuned for even more control over how multi-party agreements move through your pipeline.

Good to Know

  • Up to 6 roles can be added per template; roles are local to that specific template.

  • Roles only populate automatically when the document is sent via a Workflow (not from manual send).

  • At least one fillable element must be assigned to “Contact” for the Workflow send action to function.Role details set at the workflow level override the template’s default values.

  • If a required role email is missing, you’ll be prompted to complete it before sending. Duplicate emails across roles will trigger an alert.

  • Currently available on Web.

IMG_0240
IMG_0241
IMG_0242
IMG_0243
IMG_0244

Documents & Contracts: Collect card details

What’s New?

  • You can now collect and save card details within Documents & Contracts using the new “Card Details” field.

  • Signers can securely add their card while filling the document, and the card gets saved for future payments.

How to Use?

  • Open the document builder and click on “+ Add Element”

Screenshot 2026-03-31 at 5
  • Drag and drop the “Card Details” field into your document

  • Assign the field to a signer and mark it as required if needed

Screenshot 2026-03-31 at 5
  • Ensure a payment provider is connected and live/test mode is enabled

Screenshot 2026-03-31 at 5
  • Send the document to the signer

  • The signer clicks “Start filling out” and enters card details

Screenshot 2026-03-31 at 5
  • Card gets securely saved as soon as user selects add card and can be used later for payments

Screenshot 2026-03-31 at 6
Screenshot 2026-03-31 at 5

Note

Supported providers are - Stripe, NMI, Square, Authorize-net, Adyen;

Unsupported (Upcoming) - Razorpay , PayPal, Custom payment providers

-

Why We Built This?

  • To capture payment details upfront during document signing

  • To eliminate follow-ups and reduce drop-offs in payment collection

  • To lay the foundation for auto-pay, subscriptions, and seamless future charges

Documents & Contracts: Staff Selection in Templates

What’s New?

Earlier, while creating a template, Admins could assign signature fields only to:

  • Contact

  • Sender

  • Themselves

If you were serving a business and wanted to assign the business-side signature to a specific staff member, this was not possible.

Now, Admins can access and assign signature fields to the entire staff list directly within templates.

You can select any team member from the staff list while configuring “To be signed by”.

Screenshot 2026-02-18 at 16

How to Use?

  • Go to Templates and create or edit a template.

  • Add a Signature or any other fillable field.

  • In the right-side Properties panel, click on “To be signed by”.

  • You will now see the complete staff list.

  • Select the required team member and save the template.

The selected staff member will be assigned the signature role when the document is used.

Why We Built This?

  • To support agencies serving multiple businesses.

  • To allow assigning business-side signatories to the correct staff member.

  • To remove dependency on only “Sender” or “Contact”.

  • To make document workflows more flexible and scalable for teams.

This update gives Admins better control and improves multi-user document handling

Earlier updates