Adobe Sign Setup and Workflow
This page explains how to configure and use Adobe Sign integration with the SharePoint Connector.
Adobe Sign Overview
Adobe Sign (part of Adobe Document Cloud) provides electronic signature capabilities. The SharePoint Connector integrates with Adobe Sign to enable signing workflows directly from Business Central.
Prerequisites
Adobe Sign Requirements
| Requirement |
Details |
| Adobe Sign subscription |
Business or Enterprise tier |
| Admin access |
To configure API integration |
| API access |
API enabled on account |
Business Central Requirements
| Requirement |
Details |
| SharePoint Connector |
Installed and configured |
| SharePoint connection |
Working and tested |
| Permissions |
E-signing permission set |
Configuring Adobe Sign
Step 1: Adobe Sign Portal Setup
In Adobe Sign Admin Console:
- Log in to Adobe Sign admin
- Go to Account > API
- Create an integration key
- Note the API values needed
Step 2: Business Central Setup
- Search for "Adobe Sign Setup" in BC
- Open the setup page
Adobe Sign Setup Fields
| Field |
Description |
| Adobe Sign Active |
Enable the integration |
| Adobe Service URL |
Adobe Sign API endpoint |
| CC Emails |
Optional. Email addresses that receive a carbon copy of every agreement sent to Adobe Sign. Separate multiple addresses with a semicolon. These recipients are not signers. |
| Integration Key |
OAuth client ID (shown as "Integration Key" on the Adobe Sign Setup page; stored internally in the Client Id field) |
| Integration Secret |
OAuth secret |
| Callback URL |
OAuth redirect URL |
Step 3: Enter Configuration
| Field |
Value |
| Adobe Sign Active |
Yes |
| Adobe Service URL |
(from Adobe) |
| Integration Key |
(from Adobe integration) |
| Integration Secret |
(from Adobe integration) |
| Callback URL |
(your BC callback URL) |
Step 4: Connect and Authenticate
- Click Sign Into Adobe in Adobe Sign Setup
- Browser opens for Adobe authentication
- Sign in with Adobe credentials
- Grant requested permissions
- Return to Business Central
Step 5: Test the Connection
- Verify status shows connected
- Test with a sample document
OAuth Scopes
Adobe Sign integration uses these OAuth scopes:
| Scope |
Purpose |
| user_login:self |
User authentication |
| agreement_write:account |
Create agreements |
| agreement_read:account |
Read agreement status |
| agreement_send:account |
Send for signature |
Using Adobe Sign
Sending a Document for Signature
- Navigate to a record with documents
- Select the document in the FactBox
- Choose the e-Signing action to open the e-Signature detail page
- Configure the signing request:
- Add signer(s) email and name
- Add message (optional)
- Click Send to Adobe Sign for signature
Configuration Options
| Option |
Description |
| Signer Email |
Email address of signer |
| Signer Name |
Name of signer |
| Message |
Custom message to signer |
Carbon Copy Recipients
Two kinds of carbon copy (CC) recipients can be added to an agreement. Neither is asked to sign.
| Source |
Scope |
How to configure |
| Per document |
Only this agreement |
On the e-Signature detail page, add a recipient with type Carbon Copy |
| Setup |
Every agreement |
Enter one or more addresses in CC Emails on the Adobe Sign Setup page, separated by semicolons |
Setup-level CC recipients are useful for keeping a shared mailbox, such as a sales or contracts inbox, informed of every signing request.
After Sending
- Document is sent to Adobe Sign
- Adobe Sign sends email to signer
- Status shows "Sent to Adobe" in BC
- Track progress in e-Signature Overview
Signer Experience
What Signers See
- Email from Adobe Sign
- Link to document
- Document preview
- Signature fields
- Completion confirmation
Signing Process
- Signer clicks email link
- Reviews document
- Signs where indicated
- Submits signed document
- Confirmation sent to all parties
Tracking Status
Status Values
The status field is free text populated from Adobe Sign (except the initial value, which the connector sets itself). Typical values:
| Status |
Meaning |
| Sent to Adobe |
Set by the connector when the agreement is sent |
| OUT_FOR_SIGNATURE |
Waiting for signature |
| SIGNED |
All signatures done -- triggers automatic download of the signed PDF |
| CANCELLED |
Agreement cancelled |
| EXPIRED |
Signing period expired |
The connector reacts only to the exact value SIGNED: when a status check returns SIGNED, the signed document is downloaded automatically. There is no "Completed" status in the Adobe flow, and no other value triggers any action.
Checking Status
- Open e-Signature Overview
- Find the document
- View current status
- Use Check Adobe Sign Status action to refresh
Retrieving Signed Documents
Automatic Retrieval
When signature is complete:
- Check status shows "SIGNED"
- Use Check Adobe Sign Status - when status is "SIGNED", the signed document is automatically downloaded
- Signed PDF saved to SharePoint
- Original folder updated
Manual Retrieval
If automatic retrieval fails:
- Log in to Adobe Sign portal
- Find the agreement
- Download signed document
- Upload to SharePoint manually
Adobe Sign Best Practices
Document Preparation
| Practice |
Benefit |
| Clear signature locations |
Easy for signers |
| Professional formatting |
Good impression |
| Complete content |
Avoid amendments |
Signer Communication
| Practice |
Benefit |
| Notify signers |
They expect the email |
| Provide context |
Explain what they're signing |
| Set deadlines |
Encourage timely signing |
Troubleshooting
Connection Issues
| Issue |
Check |
| Auth fails |
Verify credentials |
| API error |
Check Adobe service status |
| Permission denied |
Verify OAuth scopes |
Sending Issues
| Issue |
Check |
| Send fails |
Valid signer email? |
| Document error |
File format supported? |
| Status stuck |
Check Adobe Sign portal |
Common Errors
| Error |
Resolution |
| Invalid email |
Verify signer email format |
| Document too large |
Check file size limits |
| API rate limit |
Wait and retry |
