You asked, and we answered.

S-Docs for Salesforce supports both per-user and per-document (consumption-based) pricing:

Per-user licensing is ideal when:

• Many documents are generated per user, or
• You anticipate diverse use cases (quotes, invoices, contracts, internal docs, etc.).

Per-document licensing is ideal when:

• A smaller group of users generates a large total volume, or
• You want tight control over document counts rather than user counts.

We’ll work with you to choose the model (or combination) that aligns best with your volume, automation needs, and budget.

The S-Docs for Salesforce free trial is designed for evaluation and low-volume use. It includes 150 generated documents and up to 50 e-Signatures with no user-count restriction. The knowledge base is available for support questions. For ongoing business use, especially where SLAs and support are important, we recommend a paid plan.

Pricing can be different between manual click-to-generate and automated, high-throughput usage:

Manual generation (button clicks, user-driven flows) may be priced lower because:

• Document volume is naturally constrained by human interaction.

Automated generation (record-triggered flows, batch jobs, scheduled runs) may be priced higher because:

• Volume can spike significantly (thousands per hour, or millions per year).
• It places a higher load and requires more capacity planning.

We’ll typically ask about:

• Annual document volume.
• Percentage that is automated vs. manual.
• Burst behavior (e.g., seasonal spikes, peak hours), then align you with a suitable package.

Paid S-Docs for Salesforce plans start at a $3,000 annual minimum, and customers need a minimum of 10 S-Docs licenses for access to the full version. Orgs with fewer than 10 Salesforce users can still purchase an S-Docs for Salesforce paid plan starting at that annual minimum price.

S-Docs for Salesforce does not offer admin/view-only/restricted licenses. Not everyone in the org must be licensed, but users who create, use, or send documents within Salesforce do need licenses, subject to the 10-license minimum for the full version.

Multi-year agreements are designed to give you predictable costs and flexibility:

• Price protection over the term (e.g., 3 years).
• Often, discounted rates vs. 1-year contracts.
• In document-based plans, we can often:
• Pool document allotments across years or users.
• Avoid “use it or lose it” within a single year, depending on the structure.

If your volume or user base is growing, we can also build growth assumptions into the contract.

Yes. S-Docs for Salesforce is a 100% native Salesforce application.

• S-Docs for Salesforce runs entirely inside your Salesforce org
• S-Docs for Salesforce uses your Salesforce data, security model, and permissions.
• S-Docs for Salesforce processes data on the Salesforce platform rather than sending core processing and data to external app servers.

For you, “native” means:

• Fewer integration points to manage or break.
• Data residency and compliance are simplified by staying in Salesforce.
• Performance and reliability aligned with your Salesforce environment.

S-Docs for Salesforce requires Enterprise, Unlimited, Performance, or Developer Edition, and is not compatible with Professional Edition or Salesforce Essentials. S-Docs for Salesforce works across many Salesforce products, including (but not limited to) Sales, Service, Experience, Health, Government, Manufacturing, Financial Services, Education, and Revenue Cloud.

By default, documents are typically stored as Salesforce Files or Attachments, as well as records in an S-Docs for Salesforce document object (still within your org). You can also:

• Move or sync generated files to SharePoint, Box, Google Drive, Amazon S3, or other repositories via integrations.
• Control where documents live based on cost, retention, and compliance needs.

We’ll help you design a storage strategy that balances Salesforce storage costs, retrieval needs, and regulatory requirements.

Yes, S-Docs for Salesforce works with both Salesforce Lightning Experience (our primary focus) and Salesforce Classic. You can place buttons, actions, and components in either UI, but we advise using our LWCs to generate and view documents in Salesforce Lightning Experience.

No, S-Docs for Salesforce does not access, transmit, or store Salesforce data on S-Docs for Salesforce servers. S-Docs for Salesforce is architected as a 100% native Salesforce app so that:

• All document generation happens inside Salesforce.
• Your data does not leave your Salesforce org to be processed.
• We do not store your customer or business data in external S-Docs for Salesforce data servers.

This is a key differentiator for organizations with strict data-handling policies.

S-Docs for Salesforce is a FedRAMP High and DoD IL5-compliant solution. As a 100% native app, it also inherits Salesforce’s security and compliance protections. See trust.sdocs.com for more information about our certifications and compliance documentation.

Because S-Docs for Salesforce runs natively in Salesforce, your data residency follows your Salesforce org:

• If your Salesforce org is hosted in the EU, documents and processing stay within that region.
• S-Docs for Salesforce does not relocate your data outside the residency region defined by Salesforce.

For GDPR and similar regulations, this is often a major advantage compared to non-native tools that process data on their own servers.

No, password-protected PDFs are not supported by S-Docs for Salesforce. For e-Signature workflows, however, S-Sign does support encrypted documents at rest with a verification-code experience, so the secure alternative is protected signed-document access rather than password-protected generated PDFs.

S-Docs for Salesforce can generate a broad set of document formats, including (but not limited to) PDF, Microsoft Word (DOC or DOCX), Microsoft Excel (XLS or XLSX), Microsoft PowerPoint (PPTX), CSV, HTML emails, XML, JSON, and more.

Yes, you can upload existing Microsoft Word templates to S-Docs for Salesforce for DOCX-based workflows. However, most complex or strategic implementations eventually migrate to the native template editor to unlock full flexibility.

The S-Docs for Salesforce template editor is built for complex use cases and can handle a broad spectrum of use cases. You can insert:

• Individual Salesforce merge fields from the base template object, related objects, and even unrelated objects.
• Related lists that behave as dynamic tables.
• Conditional logic that allows you to show/hide clauses, sections, or whole pages based on business rules.
• Reusable components that can be inserted into multiple templates, simplifying maintenance.

It’s designed to handle any enterprise document workflow, from simple notices to complex contracts, proposals, and more.

Yes, S-Docs supports:

• High-resolution images embedded in templates.
• Multiple images per document (including large photo-heavy reports and inspection documents).
• Standard asset patterns such as contact headshots, product images, logos, and more.

Image limitations include a 30 MB total image limit in a generated PDF and a 60 MB max generated PDF size, so image-heavy use cases should always be tested against the chosen output format.

Yes. S-Docs allows you to:

• Build multilingual templates that pull the correct language content based on conditional logic (e.g., output the right language based on account, opportunity, country, or user settings)
• Translate the internal S-Docs UI
• Translate merge fields and field labels, including use with Salesforce Translation Workbench.

In practice, that means the template strategy still needs to be designed thoughtfully.

S-Docs for Salesforce respects Salesforce platform limits and practical performance boundaries:

• Very large documents or extremely image-heavy templates may:
• Take longer to generate
• Be constrained by Salesforce file size limits.
• High-volume scenarios (e.g. thousands of documents per hour) may require specific architecture, batching, and throttling patterns.

Yes. S-Docs for Salesforce includes a native e-Signature capability that lives inside Salesforce. It lets you generate documents and send them for signature without leaving your org. Compared to external tools (e.g., DocuSign, Conga Sign, Nintex), S-Docs’ for Salesforce key differentiator is that both document generation and e-signing can be handled in one, fully Salesforce-native stack, reducing integrations to manage and keeping data on-platform.

Yes. Many customers use S-Docs for Salesforce for document generation and keep their current e-sign provider. S-Docs for Salesforce can hand off generated documents to DocuSign and other e-sign platforms as part of your Salesforce flows. You can maintain your existing contracts and signer experience while modernizing the document generation layer.

S-Docs for Salesforce supports flexible e-Sign workflows:

• One or multiple signers.
• One or multiple documents.
• A variety of input fields (e.g., text, date) that can be written back to Salesforce fields.
• Configurable signing order (sequential or parallel).
• In-person signing or remote signing.
• Status tracking inside Salesforce (sent, viewed, signed, etc.) with the ability to build flows that send reminders, escalate, or update records automatically.

No, S-Docs for Salesforce does not use an envelope-based pricing model. e-Signature packages come with unlimited e-Signature envelopes.

Every signed document includes a detailed audit trail that includes a SHA-256 hash, signer details, IP address, signing order, timestamps, domain history, and event history, and that audit record is appended to the finished document. Workflows and restrictions are designed to align with common e-sign laws (like the ESIGN Act), preserving document integrity after sending and ensuring compliant handling of changes and signer identity.

Both are supported. Documents can be generated manually from buttons/LWCs or fully automatically through record-triggered flows, processes, or batch jobs.

You can mix modes: some documents may be fully automated (e.g., receipts, notices), while others require a user click and review step.

• Screen flows show a UI where users can review, confirm, or add input that affects the contents of the document before generating/sending; they’re ideal when teams want hands-on control and visibility.
• Record-triggered flows run automatically when records change; they’re best when rules are well-defined and you want minimal user interaction, but users don’t see a preview unless you explicitly build one.

There is no difference in licensing between Screen Flows and Record-Triggered Flows.

Yes, users can preview generated PDFs and edit them in Salesforce, with no external tools required. Editing permissions can be configured so that only specific individuals have editing access. Version history preserves each document version after edits are made.

S-Docs for Salesforce is designed to support high-volume workloads while respecting Salesforce governor limits. For scenarios like thousands of documents per hour or millions per year, we architect flows and batching strategies to:

• Break work into manageable chunks.
• Queue or schedule generation during peak windows.
• Avoid hitting Salesforce CPU, DML, and API limits.

Your pricing and implementation plan will reflect those volume and burst requirements.

S-Docs for Salesforce itself runs online inside Salesforce, but can fit into offline-first architectures in certain cases:

• Field apps (e.g., Eureka or service apps) collect data offline.
• Data syncs back to Salesforce when a connection is available.
• S-Docs then generates documents using that synced data.

This lets you support offline field work while still centralizing document generation and storage in Salesforce. Offline use cases should be discussed with an S-Docs for Salesforce expert first.

Migration effort depends on how many templates you have and how complex they are, but S-Docs for Salesforce offers plans with template conversion support, workflow mapping, live onboarding, and expert guidance to help teams get running quickly.

Yes, you can reuse existing Microsoft Word or PDF documents by uploading them to S-Docs for Salesforce and map Salesforce data into them.

To take advantage of native features like conditional logic, complex related lists, reusable sections, and more, most customers rebuild key templates in the S-Docs for Salesforce editor and consolidate where possible.

Exact timelines depend on template count, automation, e-Signature design, security review, and whether you are rebuilding or converting existing assets.

S-Docs for Salesforce offers a robust knowledge base, an on-demand education platform, community, videos, end-user guides, and more.

Yes. Our professional services team can:

• Design or polish complex templates.
• Implement flows and automations.
• Optimize performance and handle edge cases.

Engagements are typically scoped by hours or project, with published hourly rates and clear estimates before work begins.

Paid plans include access to support (and, at higher tiers, SLAs and possibly live sessions) for troubleshooting and configuration questions.

The free plan is primarily self-service: you get the product and documentation, but not guaranteed response times or live troubleshooting. Exact entitlements depend on your chosen plan.

Yes. S-Docs for Salesforce is used for heavily audited and regulated documents, including tax-compliant donation receipts, court and judicial reports, student records, and compliance letters. Because everything runs in Salesforce, you can enforce strict templates, approvals, and logs around who generated what, when, and for which records.

S-Docs for Salesforce supports high-volume batch generation, and can be tuned for seasonal spikes such as fundraisers, big events, or enrollment periods by:

• Scheduling flows and batches for peak throughput.
• Testing ahead of critical dates to validate throughput and limits.

This ensures that high-stakes events don’t overload your document infrastructure.

Yes. You can define separate templates for:

• External documents that hide internal notes and sensitive fields.
• Internal documents that show full detail for staff.

Salesforce permissions and template logic determine which users can generate which type of document and what data appears in each, so you can safely reuse the same underlying data model for different audiences.