Help Center Getting Started Configure Dochly Settings

Configure Dochly Settings in Salesforce

Updated June 2026 8 min read Getting Started
Dochly's settings control how your org generates, stores, delivers, and signs documents at an org-wide level. Getting these right before rollout ensures consistent behavior for every user and every workflow. This guide covers all eight settings areas — what each setting does, what to configure for most orgs, and what to watch out for. Settings can be revisited and updated at any time from the Dochly Settings page.

How to access Dochly settings

All Dochly settings are accessed from a single location inside Salesforce. Only users with the Dochly Admin permission set can view and edit settings.

How to navigate there

Open the Dochly app from the App Launcher → click Settings in the top navigation bar. The Settings page is divided into sections — use the left-side navigation or scroll to reach each area.

Who can change settings

Only users with the Dochly Admin permission set can access and modify settings. Standard Dochly Users see the app but have no access to the Settings page.

Settings areas at a glance:


General settings

General settings control the fundamental behavior of document generation across your org. These are the first settings to configure after installation.

General — Settings → General

Required
Default output format

Sets the default document format for all templates. Can be overridden per template.

Recommended: PDF
Org timezone

Controls the timezone used for {{TODAY}} and {{NOW}} merge fields. Should match your Salesforce org's timezone setting in Company Information.

Recommended: Match your Salesforce org timezone
Default date format

The default format applied to date fields when no format is specified in the merge field syntax. Applied org-wide — individual templates can override this.

Recommended: MMMM d, yyyy (e.g. June 15, 2026)
Default currency format

Controls how currency fields are displayed — symbol, decimal places, and thousand separators. Matches your Salesforce org's currency settings by default.

Recommended: Keep default (inherits from org)

Document storage settings

Storage settings control where generated documents are saved after generation. Getting this right is critical — incorrectly configured storage means documents disappear after generation instead of being accessible on the record.

Storage — Settings → Document Storage

Required
Primary storage destination

Where generated documents are stored after generation. "Attach to originating record" stores documents as Salesforce Files on the record that triggered generation.

Recommended: Attach to originating record
File naming convention

Controls the filename of generated documents. A clear naming convention makes documents easy to identify in the Files list.

Recommended: [Template Name] — [Record Name] — [Date]
Version handling

What happens when the same template is generated multiple times from the same record. "Create new file" keeps all versions — "Replace existing" keeps only the latest.

Recommended: Create new file (preserves history)
Retention policy

Optional — set how long generated documents are retained as Salesforce Files. Leave blank to inherit your Salesforce org's standard file retention policy.

Recommended: Leave blank (inherits org policy)

If you change the storage destination after users have already generated documents, previously generated documents remain where they were stored. Only new generations will use the updated storage setting.


Email delivery settings

Email delivery settings control how Dochly sends documents and e-signature requests to recipients. Correctly configured email settings ensure documents reach customers and that signature request emails don't land in spam.

Email — Settings → Email Delivery

Required
From name

The sender name that appears in the email "From" field when Dochly sends documents or signature requests.

Recommended: Your company name (e.g. "Dochly Team at Acme Corp")
From email address

The email address used as the sender. Use a monitored company email address — replies from customers signing documents will go here.

Recommended: A monitored team inbox (e.g. contracts@yourcompany.com)
Email template

The body of the email sent when delivering a document or signature request. Customise the subject line, greeting, and body text to match your brand voice.

Recommended: Customise with your brand name and a clear CTA
BCC admin on sends

Optionally BCC a team inbox on every document or signature email sent. Useful for compliance-sensitive workflows where you need a record of every delivery.

Recommended: Enable for contract and legal document workflows

Dochly sends emails through Salesforce's email infrastructure — not an external email service. Your Salesforce org's email deliverability settings (Setup → Email → Deliverability) must allow "All Email" for document and signature emails to send successfully.


E-signature settings

E-signature settings control how signature requests behave — authentication requirements, signing experience options, expiry, reminders, and what happens when signing is complete.

E-signature — Settings → E-Signature

Required
Default authentication

The identity verification method used by default when sending for signature. Can be overridden per signature request.

Recommended: Email link (no additional authentication) for most workflows
Signing expiry

How long a signature request remains open before expiring. After expiry, the signer cannot sign and a new request must be sent.

Recommended: 14 days for proposals and contracts
Automatic reminders

Send automatic reminder emails to unsigned signers after a set number of days. Reduces the need for manual follow-up on outstanding signatures.

Recommended: Enable — reminder at 3 days and 7 days
On completion — store signed document

Whether to automatically store the fully signed document on the originating Salesforce record when all parties have signed.

Recommended: Always enable — this is critical for audit trails
On completion — update Salesforce record

Optionally update a field on the originating record when signing is complete — for example, changing Opportunity Stage to "Contract Signed" or checking a "Signed" checkbox.

Recommended: Enable and configure per your sales process stages
Signing consent language

The legal consent language shown to signers before they can sign. Required for ESIGN/UETA compliance. Use the default provided or have your legal team review and customize.

Recommended: Use Dochly default or legal-approved custom language

Object access settings

Object access settings control which Salesforce objects are available as primary objects in the template editor. Standard objects (Opportunity, Account, Contact, Contract, Case) are enabled by default. Custom objects must be added manually.

Object Access — Settings → Object Access

Recommended
Standard objects

Opportunity, Account, Contact, Contract, Case — enabled by default. No configuration needed unless you want to restrict which objects are available for template building.

Default: All enabled
Custom objects

Any custom objects in your org that you want to build templates from. Add each custom object by its API name (ending in __c). Once added, it appears as a primary object option in the template editor.

Add only the custom objects you actively need for templates
Related list access

Controls which related lists (e.g. Opportunity Products, Case Comments) are available for dynamic table merge fields. Standard related lists are auto-discovered. Custom related lists may need to be added manually.

Default: Auto-discover standard related lists

User permission settings

User permission settings in Dochly control what different roles can do within the platform. This is separate from Salesforce profile permissions — it's Dochly-specific access control layered on top.

Permission Set Key capabilities Assign to
Dochly Admin Create/edit/delete templates, access all settings, view all generation logs, manage permission assignments Salesforce admins and template owners only
Dochly User Generate documents from Active templates, send for e-signature, view own generation history All users who need to generate documents
Dochly Read Only View generated documents and generation history only — cannot generate new documents Managers needing visibility without generation access

Assign permission sets from Setup → Users → [User Name] → Permission Set Assignments, or use Permission Set Groups if you're assigning to multiple users at once. For bulk assignment, use the Permission Sets list view → Manage Assignments.


Branding settings

Branding settings allow you to upload your company logo and set default brand assets that can be referenced in templates. These are org-level defaults — individual templates can use their own branding independently.

Branding — Settings → Branding

Optional
Company logo

Upload your company logo (PNG with transparent background recommended, minimum 300px wide). Once uploaded, it can be referenced in templates using a logo merge field rather than uploading separately to each template.

Recommended: Upload once here for consistency across all templates
Brand colors

Store your primary brand color hex code. Used as a reference when building templates — doesn't automatically apply to templates, but makes the value accessible to template builders without needing to look it up.

Optional — useful for orgs with multiple template builders
Default fonts

Set the default heading and body font used when creating new templates. Can be overridden in individual templates.

Recommended: Match your brand guidelines font choices


Frequently asked questions

No. Settings changes only affect documents generated after the change is saved. Previously generated documents are static Salesforce Files — they are not re-generated or affected when settings change. This applies to storage, email, branding, and all other settings.
Yes. Template-level settings override org-level settings for that specific template. For example, you can set the org default output format to PDF but configure a specific template to generate as DOCX. Template-level settings always take precedence over org-level defaults.
First, check Salesforce Setup → Email → Deliverability — it must be set to "All Email" not "System Email Only". Second, verify your Salesforce org has SPF and DKIM configured for your sending domain — this significantly improves deliverability. Finally, check the "From Email" address in Dochly Settings → Email Delivery — using a domain that matches your org's verified sending domain helps avoid spam filters.
Org-level settings apply to all users and all templates by default. For team-specific settings, use template-level overrides — configure each template with the settings appropriate for that team's workflow. For example, the Sales team's proposal template can have different email sender settings than the Finance team's invoice template.

Dochly is now fully configured and ready for your team. Final step: Dochly quick start checklist — run through the complete checklist to confirm every step from installation to first generated document is complete before your full team rollout.

Dochly
Salesforce AppExchange — UTECH HUB Install Dochly on AppExchange

Rated 5 stars · Native Salesforce app · Free to install