WelisaWelisa DocGen
v1.1.0 welisa.com
Getting started

Installation & setup#

Everything a consultant or administrator does once per org: install the package, assign permission sets by role, verify the licence, and complete the post-install checklist.

Version1.1.0 (package version 1.1.0.1), released 2026-09-24. Orgs on 1.0.0 upgrade in place — see Upgrading.
Production / Developer Editionhttps://login.salesforce.com/packaging/installPackage.apexp?p0=04tP6000003jGLRIA2
Sandbox / scratch orghttps://test.salesforce.com/packaging/installPackage.apexp?p0=04tP6000003jGLRIA2
Salesforce CLIsf package install -p 04tP6000003jGLRIA2 -o <org> -w 30 --no-prompt

Older versions and what changed in each: Release notes.

Warning

Never install Welisa DocGen into an org that already contains the same components as unpackaged source (a development org where the package was deployed from source): the installer collides with them. An org lives on one track for its lifetime — source-deployed or package-installed.

Install the package#

  1. Log in to the target org and open the install link for its host (production → login.salesforce.com, sandbox → test.salesforce.com). Check the org Id — sandbox versus production is the classic mix-up.
  2. Accept the orange AppExchange notice (Welisa DocGen is distributed directly by Welisa and is not listed on the AppExchange), choose Install for Admins Only, and wait for the confirmation e-mail (2–5 minutes).
  3. The install brings the merge engine, all Lightning components, custom objects, permission sets, the e-signature Visualforce pages, the signature seam and the licence check. A post-install script seeds the default e-mail templates and schedules the nightly licence check — there is no manual bootstrap step.

Permission sets by role#

Assign deliberately — never use the select-all checkbox on the assignment screen (see the warning below).

RoleAssignWhat they can do
Administrators and template authorsWelisa Admin + Welisa SigningFull control of templates, query configurations, assets, brands, e-mail templates, signature settings. Sign In Person bypass. The Welisa Licence tab.
Users who generate documents and send for signatureWelisa User + Welisa SigningSee every active template in the picker, generate single and bulk documents, create signature requests, use the Send for Signature action. Cannot create or edit templates or settings.
Users who only generate documentsWelisa UserAs above, without the signature features.
The site guest user (external signers)Welisa Guest SignatureRead access to signature requests, signers and placements; create access on audit records; the signing pages. Assigned on the e-signature site's guest user — see E-signature setup.
Admins who manage record-page buttonsWelisa Button Manager (plus Salesforce's Customize Application permission)The Buttons tab in the Command Hub. Deliberately separate from Welisa Admin because it deploys custom metadata.
Only the one-click buttonWelisa Quick ActionGrants the quick-action button on its own, for users who need nothing else.

Welisa Signing is the signature seam: it carries the Send for Signature quick action, the Welisa Envelopes tab and the Welisa Licence tab. Assign it to anyone who sends documents for signature, and to every administrator.

Command line:

sf org assign permset -n welisa__DocGen_Admin -n welisa__DocGen_Signing -o <org> -b <admin-username>
sf org assign permset -n welisa__DocGen_User -o <org> -b <user-username>

Assigning a permission set in Setup#

  1. Setup → Users → Permission Sets.
  2. Click the permission-set name (for example Welisa Admin).
  3. Manage Assignments → Add Assignments.
  4. Tick each user → Next → Assign.
Warning

Welisa User includes read-only View All on Welisa Template so every user sees all active templates without sharing rules. Some Salesforce user licences — Chatter Free, Identity, and Customer/Partner Community among them — do not permit View All Records on a custom object. Assigning Welisa User to those users is not just unnecessary (they cannot generate documents anyway); it will block your next package upgrade, because Salesforce re-validates every assignment against its licence when the permission set changes. Find offending assignments before upgrading:

SELECT Assignee.Name, Assignee.Profile.UserLicense.Name
FROM PermissionSetAssignment
WHERE PermissionSet.Name = 'DocGen_User'

Remove Welisa User from any user whose licence is not a full Salesforce licence. The same applies to Welisa Admin, which carries View All on more objects — keep it on genuine administrators only.

Custom fields on Welisa DocGen objects#

You may add your own fields to Welisa Template, Welisa Signature Request, Welisa Signer or any other package object. Grant field-level security on all affected permission sets in the same change (Admin, User, Guest Signature). A missed grant silently breaks field access for that role.

Verify the licence#

Open the Welisa DocGen app → Welisa Licence tab. It must read Licensed. There are no licence keys and nothing to configure in the org: it registers itself during the install. If the tab does not read Licensed, press Check now once; if it still does not, contact Welisa with the org Id.

Post-install checklist#

  1. Permission sets assigned by role (above).
  2. PDF rendering release update enabled — Setup → Release Updates → "Use the Visualforce PDF Rendering Service for Blob.toPdf() Invocations" → Get Started → Enable. Mandatory for PDF output; see Troubleshooting if the button reads Enable Test Run.
  3. Welisa Licence tab reads Licensed.
  4. Open the Welisa DocGen app. The Command Hub is the home base for templates, bulk jobs, assets, brands, e-mail templates and signature settings. See Administration.
  5. Check the Type picklists. A fresh install contains every template type (Word, PowerPoint, Excel, HTML, PDF, Canvas) on both Welisa Template and Welisa Template Version. If an upgraded org is missing a value, add it by hand — Troubleshooting.
  6. Place the record-page components — Lightning App Builder → the object's record page → drag on Welisa Runner (generate documents) and, if the client signs, the Send for Signature quick action and/or the Welisa Signature Sender component. Save and activate. See Generating documents.
  7. E-signatures only: complete the one-time E-signature setup — site, sender address, guest permission set, e-mail deliverability — before the first signature request.
  8. Create a first template — a starter design is the quickest smoke test (Quick start).

Templates after install#

A fresh install contains no document templates: templates are records (a template, a template version and a file), and records cannot ship inside a managed package. Three ways to get going:

  1. Starter designs — Command Hub → Create New → Start from a Design: Record Report (Account), Invoice / Line Items (Opportunity), Business Letter (Contact), Agreement (Account), Certificate. Standard fields only.
  2. Welisa's template library — Welisa maintains generic, Welisa-styled templates (quote, invoice, order confirmation, timesheet, NDA) that a consultant adapts to the client's fields. Ask your Welisa consultant.
  3. Bring your own — upload the Word or HTML documents the client already uses and add merge tags. See Templates.

What the install adds to the org#

KindItems
AppWelisa DocGen (Command Hub, Templates, Jobs, Signature Requests, Signers, Signature Audits, Error Logs, Welisa Licence)
Objects (welisa__ prefix)DocGen Template, Template Version, Job, Saved Query, Asset, Brand, Email Template, Error Log, Signature Request, Signer, Signature Placement, Signature Audit, Envelope, License (protected setting), Settings (custom setting), Button (custom metadata), Signature Setting (custom metadata)
Lightning componentsWelisa Runner, Welisa Button, Welisa Signature Sender, Send for Signature (quick action), Welisa Setup Wizard, Welisa Button Builder, Welisa DocGen Licence
Flow actionsGenerate Document, Generate Bulk Documents, Generate Document (Auto Giant Query), Welisa: Create Signature Request, Welisa: Send for Signature, Welisa: Write Back Signer Form Fields, Validate Signature Token, Submit Signed Signature, Finalize Signature Image
Visualforce pagesDocGenSignature, DocGenSignaturePdf, DocGenVerify, DocGenSign (the public signing and verification pages)
Scheduled jobsWelisa Licence Check (nightly), DocGen Signature Reminders (hourly, when reminders are enabled), DocGen Chart CV Reaper (daily cleanup of transient chart files)
Remote site settingDocGen_License_Server — the licence service at license.welisa.dev; the only outbound connection the package makes

Next steps#