Skip to main content
Skip table of contents


DocuFetch provides document collection by providing a way to:

  • Create a request asking for particular documents to be uploaded

  • Send the request link to a user outside of Salesforce, which will provide an upload button for each requested document

  • Allow the user to upload one or more documents, including documents that are pre-filled in via merge fields and documents that have been signed via e-signature by the user

  • Approve or reject the received documents, and request another document if one is rejected

  • Store the user-uploaded documents in S-Drive

  • Create document request templates to be used over and over again

See the DocuFetch User Guide for information about using DocuFetch.


Use Case: Requesting Documents

Let’s say you run a company that provides temporary workers for other companies. You need applicants to submit several different documents to your program:

  • Application

  • Driver’s license or other ID

  • List of references

  • Resume

  • Sign a form with some information

With DocuFetch, you can create a Request template that has each of those items in it. You can then use the template to create a Request, and send the Request link to an applicant, asking them to upload the required documents and sign the document that needs a signature. When you receive the documents, you can take a look at them and either accept them or reject them. If rejected, you can send the request back to the applicant and ask them to try again.

When the documents are uploaded, they are stored in S-Drive for easy, organized access.

Providing Documents Requested

When the requestee receives a DocuFetch request link, they can click the link and see a page with each item that is requested. For each item they can click the corresponding button to complete the request--upload, fill in form, or e-sign.

They will see a progress bar for the request and a status for each item as they complete the request.

For information on how to use DocuFetch after it is configured, see DocuFetch User Guide


For basic document requests

  • S-Drive 2.25 or later

  • S-Drive Public Share/surl feature

    • In Step 2 of “S-URL and Public Share Setup” from the link above, give the created user Create/Read/Edit/Delete access to the following objects as well.

      • SDriveDocumentIntakeRequest,

      • SDriveDocumentIntakeRequestItem,

      • SDriveIntakeRequestItem_Template

      • SDriveIntakeRequest_Template

For Form Completion and/or E-Signature

DocuFetch Setup in Salesforce

DocuFetch can be used out-of-the-box on Accounts, Cases, Opportunities, Contacts, and Leads. If you are creating document requests from any of those objects, skip to Step 2.

1. Add a lookup field if using a custom object

Skip this step if you are using DocuFetch on Accounts, Cases, Contacts, or Opportunities.

You must define a relationship between your object and DocuFetch with a lookup field on SDrive Document Intake Request:

  1. Go to Setup

  2. In Object Manager, find SDrive Document Intake Request object

  3. Go to Fields and Relationships and click New

  4. Add a Lookup field to your custom object

2. Add DocuFetch to your object Lightning page

Edit the Lightning Record Page of an object you want to use DocuFetch with. In the example, we’ll use Account.

Drag the SDrive DocuFetch component onto the Page.

Click into the component and fill in the configuration as follows:

  • Title: The heading that will show on the component. If blank, the heading will be DocuFetch Requests

  • File Object Prefix: For S-Drive out-of-the-box objects (Account File, Case File, Contact File, Lead File, Opportunity File) this will be cg__. For Custom object files, it will be blank unless the object is part of another managed package.

  • File Object Name: the S-Drive File object where DocuFetch files will be stored, such as AccountFile__c.

  • Parent Object Relationship Name: The API name of the lookup field from Document Request object to the object you’re relating it to. In this example, we’re using DocuFetch on Account, so the lookup field is cg__Account__r. For a custom object, it’s the name of the field you set up in Step 1.

Save the settings and Go Back to the Account Page. Now you’re ready to create a Request Item.


DocuFetch users (those who create requests) need profile permission on all DocuFetch objects as well as the S-Drive object they’re using S-Drive on.

  • SDrive Document Intake Requests

  • SDrive Document Intake Request Items

  • SDrive Intake Request Item Templates

  • SDrive Intake Request Templates

DocuFetch request links are accessed via S-Drive Public Share. Therefore the Public Share user needs profile permission on all the above objects also. See S-URL and Public Share Setup for how to set up Public Share.

Formstack Configuration for DocuFetch

Some features of DocuFetch require Formstack integration.

For Generate Document, Complete Form, and Complete E-Signature features*

Formstack Installation:

Formstack - Native form builder & data collection for Salesforce can be installed directly from AppExchange. It is only needed if you want to generate pre-filled forms.

Formstack Documents (formerly WebMerge) - Document Generation + Formstack Sign can also be installed directly from AppExchange. It is needed to generate forms with merge fields and send requests for e-signature.

Read more about Formstack integration with Salesforce.

Documents + Sign:

Formstack Document Intake Component Setup in Salesforce

  1. Enable Formstack for file object that will use Document Intake


  2. Use the same API credentials of Formstack account that you’ll use in the 2nd step of Formstack Setup.

AdobeSign Setup in Salesforce

Package Installations and S-Drive Configurations

  1. Install Adobe Acrobat Sign eSignatures for Salesforce from AppExchange

  2. Install SDrive ASign Package (Contact Sales or Open a Support Ticket to get the package)

  3. Setup Public Share (see next section)

  4. Add Remote Site Settings and Trusted URL endpoints:



  5. EAdobe Acrobat Sign for the E-Signature Service of DocuFetch. SDriveConfiguration → Micro Services → E-Signature Configuration.


Adobe Acrobat Sign Configuration

  • From the Salesforce App Launcher, go to the Adobe Acrobat Sign for Salesforce and click on the Adobe Acrobat Sign Admin tab to connect your Adobe account to Salesforce. Use Sign in to Adobe to continue and make sure the checkbox Enable Adobe Analytics and add * to CSP trusted sites is enabled.

Ekran görüntüsü 2024-04-17 131756-20240417-101831.png
  • You’ll see the success page. Click Next.

  • The Automatic Status Updates setting has to be enabled so that agreements can be sent

    Ekran görüntüsü 2024-04-17 135241-20240417-105300.png
  • Return to the Adobe Acrobat Sign Admin tab. Click Generate Sample Self Sign Agreement Template to create a template. Use the Attachment tab to upload the document you want to send, and the Recipient tab to select who you want the agreement sent to. See for more details.

    Ekran görüntüsü 2024-04-17 135557-20240417-105614.png

  • Assign permission sets for the community user. The Adobe Acrobat Sign Community User permission set should be the community user that you’ve created in the SURL setup.

    Ekran görüntüsü 2024-04-17 142952-20240417-113030.png

  • Enable Allow Sending on Behalf of Others custom setting.

    • Go to Setup-->Custom Settings

    • Find Adobe Sign Settings and click Manage next to it

    • Click New

    • Check the box next to Allow Sending On Behalf of Others

      Ekran görüntüsü 2024-04-17 145038-20240417-115052.png

  • Enable “Allow Sending on Behalf of” for the admin (who has the Adobe Acrobat Sign license). Before enabling it, you’ll need to configure the page layout of the User. Go to User from the Object Manager, and select User Page Layouts.


  • Go to the Admin user and edit it. Below enable Allow Sending As Other Users

    Ekran görüntüsü 2024-04-17 145732-20240417-115744.png

  • Create a new Agreement Template You can configure object, attachment, and recipient fields as you wish. In the recipients tab, set the admin user id to Send on behalf of. This configuration is for sending agreements using the admin user’s license, otherwise license error is given.

    Ekran görüntüsü 2024-04-17 150406-20240417-120418.png

  • Grant access to the SURL community profile for Adobe Acrobat Sign objects and fields. Make OWD public read/write for Agreement Object. CRUD and FLS permissions should be set for the following objects:

    • Agreement Template (echosign_dev1__Agreement_Template__c)

    • Agreements (echosign_dev1__SIGN_Agreement__c)

    • Merge Mapping (echosign_dev1__SIGN_Merge_Mapping__c)

    • Data Mapping (echosign_dev1__SIGN_Data_Mapping__c)

  • Enable Add Signed PDF as Separate Attachments to save signed PDFs as salesforce files. Custom settings → Adobe Sign Agreement Update Setting → New


  • Because the community user sends agreements for signature using the admin user’s Adobe license, the community user should access the admin profile.

    • Open Dev Console

    • Query the Adobe Admin User with this query: SELECT Id, Username, Email, UserPreferencesShowEmailToExternalUsers FROM UserWHERE Id = '005xxxxxxxxxxxx' where the Id is the record id of the user

    • Double click on the field UserPreferencesShowEmailToExternalUsers  and check the box.

    • Click Save Rows

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.