Prerequisites

Before you begin, you'll need:

• A Business Central environment with permission to install extensions
• Access to your organization's DocuSign account (with API/Integration access enabled on your DocuSign plan)
• A NAV SEAL license for eSignature DocuSign (requested during setup if you don't have one yet)

Installing the Extension

1. Go to Extension Management.
2. Select Upload Extension and install eSignature DocuSign.
3. No separate app needs to be installed — the license and DocuSign connection logic are built into the extension itself.

Running the Setup Guide

1. Open Extension Management, find eSignature DocuSign in the list, and select Set up this app (or search Assisted Setup and choose it from the checklist).
2. Step 1 – Welcome. A short introduction to what the guide covers.
3. Step 2 – Connect to DocuSign.
   • Select Open DocuSign Apps & Keys to open DocuSign's admin page in your browser and locate your User ID and API Account ID.
   • Enter both values, then select Connect to DocuSign — this opens a DocuSign sign-in and consent screen in your browser. Sign in and approve access, then return to Business Central.
   • Select Refresh Status to confirm Connection Status shows Connected. If it shows Failed, see the Diagnosing a Failed Connection article below.
4. Step 3 – Activate Your License.
   • Your environment's Tenant ID is detected automatically.
   • Select Request a License to send NAV SEAL an email with your Tenant ID and company details pre-filled.
   • Once NAV SEAL confirms activation, return and select Refresh Status — License Status updates to Active.
5. Step 4 – Notifications (optional). Select Notification Setup to configure who's emailed when a document completes, is declined, or voided — or skip this and configure it later.
6. Step 5 – All Set. Turn on Activate DocuSign now to let users send documents immediately (this also schedules the background job that keeps envelope statuses current). Select Finish.

You can re-run this guide at any time — for example, after rotating your DocuSign API keys — using Run Setup Guide on the DocuSign Administration page. Running it again never overwrites report or anchor settings you've already configured.

The DocuSign Administration Page — Overview

Day-to-day configuration lives on the DocuSign Administration page (search for it by name, or reach it from Run Setup Guide once initial setup is complete). It's organized into the areas below.

Setting Up: General & Connection

• Active — controls whether users can send documents at all. Turn it off any time to pause the integration without losing any configuration.
• DocuSign Connection — shows whether consent to connect with DocuSign is currently granted and verified.
• Other Actions available here: Request App Consent, Test Connection, and Revoke App Consent — the same connection actions available in the Setup Guide.

Setting Up: License

• View License Status and Tenant ID.
• Request a License and Refresh License Status mirror the actions in the Setup Guide.
• A function key ships with the extension already — nothing needs to be entered here for licensing to work. The function key fields are for advanced cases only, such as NAV SEAL asking you to use a specific replacement key.

Setting Up: Conditions

Optional guardrails, configured under Conditions:

• Require Sales and/or Purchase documents to be Released before they can be sent for signature.
• Whether Cc recipients receive a copy once an envelope is completed.
• Whether DocuSign's Certificate of Completion (Summary) document is saved as an attachment alongside the signed document(s).

Setting Up: Default Anchor

Controls where the signature field is placed on a document by default — the text to anchor to, plus an X/Y pixel offset from it. Individual reports can override this under Report Parameters if a particular layout needs the signature field placed elsewhere.

Setting Up: Templates

• Turn on Templates Active to enable DocuSign Templates.
• Once active, Sync Templates, DocuSign Templates, DocuSign Template Roles, and Doc Type Template Setup become relevant.
• The Envelope Wizard is used for every envelope automatically — there's no separate setting for it.

Setting Up: Standard Attachments

1. Turn on Standard Attachments Active.
2. Open Standard Attachments (action next to the toggle).
3. Add a row per document: Import File uploads it.
4. Use Active on each row to control whether it's currently attached to new envelopes — turn a row off rather than deleting it to pause it temporarily.
5. Every Active row attaches automatically the moment a new envelope reaches its Attachments step, for both the standard flow and Template sends.

Setting Up: Keeping Envelope Statuses Current

• Last Status Update shows when statuses were last refreshed, updated automatically each time.
• JobQueue Check Window overrides this — set it (e.g. -2D) to have every refresh search DocuSign starting that many days before today, regardless of when it last ran. Leave it blank to search from Last Status Update instead. When set, Last Status Update is greyed out since it's no longer used.
• JobQueue Setup / View JobQueue schedule and show the background job that keeps statuses current.

Setting Up: Notifications

1. Select Notification Setup.
2. For each of the four event rows (Completed, Declined, Voided, Delivery Issue), turn on Email Active and set a Notify Type: User, Fixed Recipients, or Document Salesperson/Purchaser.
3. Optionally add CC Recipients / BCC Recipients.
4. Use Test Email to confirm delivery before relying on a live envelope.
5. One-time admin step: search Email Scenario Assignment, find DocuSign Envelope Completed Notification, and assign it a connected Email Account — notifications won't send until this is mapped.

If email delivery fails repeatedly for a status, it's auto-disabled after a configurable number of consecutive failures (Notification Failure Threshold, 5 by default). Turn Email Active back on to resume and reset the count.

Setting Up: Default Email Information & Placeholders

• Set default E-mail Subject and Body text per document type — always editable per envelope afterward.
• %1 always represents the document number. Add more placeholders (%2, %3...) in the Placeholders grid, each pointing at a field on that document type's record (customer name, amount, due date, etc.).
• If a placeholder's mapped field can't be resolved for a given envelope, it's left as plain text (e.g. %2) in the message rather than disappearing silently — making a broken mapping easy to spot.

Setting Up: Confidential Document Access

1. Mark individual templates Confidential on DocuSign Templates (see the Templates how-to article for the full flow).
2. From the Setup Guide's Confidential Documents step (or Business Central's Users page), assign each user the appropriate permission set:
   • DocuSign Admin (Confidential) or DocuSign User (Confidential) — full access to Confidential content.
   • DocuSign User (Restricted) — sees that a Confidential item exists, but not its content.
3. No separate Security Filter setup is needed — this is the only step required.

Note: only the two original, unmodified permission sets grant Confidential access. A copied or renamed permission set — even with identical table permissions — does not.

Setting Up: Logs & Diagnostics

• API Log — the exact request/response exchanged with DocuSign, for troubleshooting.
• Envelopes / Envelope Logs — review everything that's been sent.
• Help & Support — opens NAV SEAL's knowledge base for this extension, or a direct support contact.

Diagnosing a Failed Connection

If Connection Status shows Failed, check the following in order:

1. Consent wasn't completed — the DocuSign sign-in/consent window was closed, blocked by a pop-up blocker, or you signed into the wrong DocuSign user. Select Connect to DocuSign again and complete the screen fully.
2. User ID or API Account ID mismatch — both must match DocuSign's Apps and Keys page exactly, character for character. Re-copy them and try again.
3. Wrong DocuSign account or environment — a Demo/Developer DocuSign account can't connect through a Production Business Central setup, and vice versa.
4. API access not enabled — not every DocuSign plan includes eSignature API access by default; check with your DocuSign account admin.
5. Network blocked — in Sandbox, confirm Allow HttpClient Requests is on for the extension; in Production, check with IT for a firewall/proxy blocking outbound calls to DocuSign.
6. DocuSign temporarily unavailable — check status.docusign.com if the above don't apply.

Open API Log after a failed attempt for the exact detail, or include it when contacting Help & Support.