Everything people ask, answered in one place - including the awkward ones.

Savvy DocGen is a Salesforce document generation and e-signature connector built by Savvy Data Cloud Consulting. It fills your Word or PDF template with data from a Salesforce record, files the finished document on that record, sends it for signature through Circularo, and writes the signed PDF back to the same record.

No. It connects to your org through a standard authorised connection, so there is no package for your security team to review and nothing installed into production.

Connecting your Salesforce org and your Circularo account takes minutes. The real work is the first template - mapping fields and placing signature marks. After that, each new template is a copy-and-adjust job.

Yes, and we recommend it. Sandboxes connect exactly like production and every feature behaves identically. You can run real templates against real sandbox records, including live signing, before anything touches production.

One template you produce often, and one record it would be built from. Thirty minutes is enough to see it generate, get signed and land back on the record.

Yes. Documents can be filed to Salesforce Files or the classic Notes & Attachments related list, set per template, so it fits whichever your processes are built around.

Yes. Any object your user can see, standard or custom - including the one your team invented three years ago - along with related records and lookup fields.

Five levels of parent lookups, plus child and grandchild records. From an Opportunity you can reach Account, then Owner, then Manager, then Profile, while line items and the products behind them come through as repeating table rows.

Any number, production and sandbox alike, with no per-org licence. Each org keeps its own templates, automation rules and signing setup, and nothing crosses between them.

A button on the record, or a rule that watches for a stage change, a field change, or a new file arriving. It is set per template, so different documents can work differently.

Yes. It reads Salesforce as an authorised user. Anything that user cannot see does not reach the document.

The query adjusts and retries rather than failing the whole document. A field that no longer exists is dropped from the query instead of breaking generation.

They can be connected, but only one deployment should ever act on a given org. Two active pollers on the same org will both send, which produces duplicates. It is a configuration rule, not a limitation of the product.

Word (.docx) and PDF. You upload the file your team already uses and it keeps its own formatting, styles and letterhead.

Yes. Conditional sections print only when the record says they should, repeating tables expand one row per child record, amounts format in the record's own currency, and images can be pulled from fields.

Up to 40 MB, including merged bundles.

Salesforce caps a single Notes & Attachments file at 25 MB. It is a property of the object and cannot be raised, so anything larger has to be filed in Salesforce Files. The product warns you at the moment you choose that store.

Wherever you tell it to, per template: Salesforce Files (ContentDocument) or Notes & Attachments. The signed copy is filed in the same place and named after the original, so the pair stay together.

Yes. Filename patterns are built from the record, so a document can be called Acme Corp - Renewal - 2026.pdf rather than something nobody can find later.

Yes. Bundles merge a set of templates into a single document in the order you set, with individual templates included or skipped based on the record. The recipient signs once and it is filed back as one file.

Yours. Signing runs through your own Circularo subscription, under your organisation's terms and retention rules. We never sit between you and your signed documents.

One API token. Paste it once and the two systems stay in step from then on - documents go across and signing status comes back to the Salesforce record.

Anchor tags placed on the template. They travel with the content, so a signature block stays correct when the document grows, shrinks or repaginates - unlike fixed coordinates, which break the moment a clause is added.

Yes. Sequential or parallel, with signers resolved from fields on the record rather than typed in by hand.

A signer can be required to enter a one-time code sent to their email address before the document opens, and the document itself can carry a per-signer password read from that signer's own Salesforce record - so a forwarded link is useless.

The document stays open and its status stays visible on the Salesforce record, so the owner can see exactly who it is waiting on. Automatic reminders can be sent on a schedule you choose.

That depends on your jurisdiction and the document type, and it is a question for your own advisers. The signature, its audit trail and its evidential weight come from Circularo under your subscription. We do not provide legal advice on validity.

Hashed with bcrypt at work factor 12. They are never stored in readable form and cannot be recovered. Length, character requirements and expiry are set by your administrator and enforced server-side.

Yes. Time-based codes from any standard authenticator app, enrolled by QR code, with single-use recovery codes. The shared secret is encrypted at rest and never returned to the browser after enrolment. It can be required across a tenant rather than left optional.

Encrypted with AES-256-GCM using a per-value initialisation vector and an authentication tag, so tampering is detectable. They are masked when read back and never displayed again after entry.

Yes. Each identity carries a version number checked on every request. Resetting a password or forcing a logout invalidates every existing session everywhere, immediately.

Yes - OIDC with the Authorization Code flow and PKCE, verified against your provider's published keys, plus SCIM 2.0 user provisioning. Both are enabled per tenant. SAML is deliberately out of scope.

Not currently. The underlying controls are implemented, but no SOC 2 or ISO 27001 audit has been completed and no third-party penetration test has been carried out. Automated dependency and static code scanning run on every change. We would rather tell you now than have it surface in a questionnaire.

In the region you require. Deployment region is a configuration choice, including the Middle East.

01 Document Generation produces documents and files them on the record. 02 Generation + Circularo adds a live connection to your signing account with status reported back. 03 End to End runs the whole loop, sending for signature and filing the signed copy back automatically.

Document Generation. For most teams the document is the problem long before the signature is, and the majority of features sit in that first level anyway.

Yes, and nothing is rebuilt. The templates and rules you configured keep running exactly as they are - the higher levels add steps rather than replacing them.

Pricing depends on the service level and the size of your team. We quote after a short conversation rather than publishing a per-document meter.

If you sign through a different provider and intend to keep it, if the document pulls nothing from Salesforce, if the logic is genuinely unique to your business, or if you send only a handful of documents a year. In each of those cases we will tell you so.

From inside the product, where the request arrives with your account context attached and reaches the right person.

Documents cannot be sent, and the product reports that as the reason rather than failing vaguely. Resolving capacity is between you and Circularo, since the subscription is yours.

Yes. The first template is where the work is, and it is the natural thing to do together on a call.

Check the status on the Salesforce record first - sent, opened, signed and filed all appear there with timestamps, and that usually identifies which step stopped. If it does not, raise a ticket from inside the product.