Participant
What's New
Get Started
Administer
- Admin Console Overview
-
User Management
- Adding users
- Create function-focused users
- Check for users with provisioning errors
- Change Name/Email Address
- Edit a user's group membership
- Promote a user to an admin role
- User Identity Types and SSO
- Switch User Identity
- Authenticate Users with MS Azure
- Authenticate Users with Google Federation
- Product Profiles
- Login Experience
-
Account/Group Settings
- Settings Overview
-
Global Settings
- New Recipient Experience
- Self Signing Workflows
- Send in Bulk
- Web Forms
- Power Automate Workflows
- Library Documents
- Collect form data with agreements
- Limited Document Visibility
- Attach a PDF copy of the signed agreement
- Include a link in the email
- Include an image in the email
- Files attached to email will be named as
- Attach audit reports to documents
- Merge multiple documents into one
- Download individual documents
- Upload a signed document
- Set a default time zone
- Users in Multiple Groups (UMG)
- Group Administrator Permissions
- Replace recipient
- Audit Report
- Transaction Footer
- Healthcare customer
- Account Setup
-
Signature Preferences
- Well formatted signatures
- Custom Terms of Use and Consumer Disclosure
- Navigate recipients through form fields
- Restart agreement workflow
- Decline to sign
- Allow signers to print and place a written signature
- Require signers to use a mobile device to create their signature
- Request IP address from signers
- Digital Signatures
- Electronic Seals
- Digital Identity
-
Report Settings
- Security Settings
-
Send settings
- Require recipient name when sending
- Lock name values for known users
- Allowed recipient roles
- Allow e-Witnesses
- Recipient groups
- CCs
- Recipient Agreement Access
- Field flattening
- Modify Agreements
- Private messages
- Allowed signature types
- Reminders
- Send Agreement Notification through
- Signer identification options
- Content Protection
- Signing order
- Liquid mode
- Bio-Pharma Settings
- Notarization Settings
- Payments Integration
- SAML Settings
- Data Governance
- Time Stamp Settings
- External Archive
- Account Languages
- Email Settings
- Migrating from echosign.com to adobesign.com
- Configure Options for Recipients
-
Guidance for regulatory requirements
- Accessibility
- HIPAA
- GDPR
- 21 CFR part 11 and EudraLex Annex 11
- Healthcare customers
- IVES support
- "Vaulting" agreements
- EU/UK considerations
- Claim your domain
- Report Abuse links
Send, Sign, and Manage Agreements
-
Recipient Options
- Cancel an email reminder
-
Options on the e-signing page
- Overview of the e-sign page
- Open to read the agreement without fields
- Decline to sign an agreement
- Delegate signing authority
- Download a PDF of the agreement
- View the agreement history
- View the agreement messages
- Convert from an electronic to a written signature
- Convert from a written to an electronic signature
- Navigate the form fields
- Clear the data from the form fields
- E-sign page magnification and navigation
- Change the language used in the agreement tools and information
- Review the Legal Notices
- Adjust Acrobat Sign Cookie Preferences
- Send Agreements
-
Authoring fields into documents
- In-app authoring environment
- Create forms with text tags
- Create forms using Acrobat (AcroForms)
- Fields
- Authoring FAQ
- Sign Agreements
- Audit Report
- Reporting and Data exports
Advanced Agreement Capabilities and Workflows
- Webforms
- Reusable Templates
- Transfer ownership of web forms and library templates
-
Power Automate Workflows
- Overview of the Power Automate integration and included entitlements
- Enable the Power Automate integration
- In-Context Actions on the Manage page
- Track Power Automate usage
- Create a new flow (Examples)
- Triggers used for flows
- Importing flows from outside Acrobat Sign
- Manage flows
- Edit flows
- Share flows
- Disable or Enable flows
- Delete flows
-
Useful Templates
- Administrator only
- Agreement archival
- Webform agreement archival
- Agreement data extraction
- Agreement notifications
- Agreement generation
- Custom Send workflows
- Share users and agreements
Integrate with other products
- Acrobat Sign for Salesforce
- Acrobat Sign for Microsoft
- Other Integrations
- Partner managed integrations
- How to obtain an integration key
Acrobat Sign Developer
- REST APIs
- Webhooks
Support and Troubleshooting
Limit recipient visibility of documents
The Limited Document Visibility (LDV) settings allow an agreement to contain multiple files that are selectively visible to the recipients depending on which settings are enabled and how the agreement is configured.
Example use cases include:
- Sales agreements that require internal oversight/approval before being sent to the customer.
- New hire documentation that is to be delivered after the offer letter is accepted.
- HR documents that require internal processing outside of the scope of the initial signer.
Here's a quick video that captures the high-level use:
How document visibility works
LDV rules are enabled at the account/group level.
LDV rules only expose the file content that has been explicitly assigned to any given recipient.
File content is assigned to a recipient by adding at least one field assigned to that recipient.
- LDV is file-based, not page-based. If a file has 40 pages, and the recipient has one field assigned to them on one page, the recipient can see all 40 pages of the file.
- If the file contains no fields for the recipient, the entire file is excluded from that recipient's view.
- If there are four files, and the recipient needs to see all four, then at least one field must be applied to one of the pages of each file.
- If page-level control is required, then the file must be broken up into individual files, each containing one page.
In the example to the right, there are two signers, and two documents in an agreement.
Signer 1 sees both documents, as there is a field assigned on both docs (Field 1 and Field 2)
Signer 2 will only see Doc 2 because they do not have an assigned field on Doc 1.
- Doc 2 is visible because Field 3 is assigned to Signer 2.
LDV rules expect two prerequisites:
- There must be more than one recipient
- Recipients include any user added to the signature/approval process
- CC'd parties are not recipients.
- There must be more than one file added to the agreement
- Files are any attachment used to build the agreement (.doc, .xls, .pdf, .png, etc)
If either of the above requirements is not in true, LDV rules are suspended for that agreement.
Configure Options
When enabled, LDV has three settings that modify the behavior of the agreement and how it is viewed:
Signers will only see files containing signature, initials or data entry fields assigned to them is the root setting that enables the LDV experience and set of controls. If
Signers will only see files containing signature, initials or data entry fields assigned to them is disabled, LDV as a whole is disabled in the recipient experience.
All recipients and CC'd parties see all files all the time.
|
During Signing |
Completed Agreement |
---|---|---|
Sender |
All documents |
All documents |
Internal Recipient |
All documents |
All documents |
External Recipient |
All documents |
All documents |
Internal CC |
All documents |
All documents |
External CC |
All documents |
All documents |
External Archive Recipient |
NA |
All documents |
Visibility of documents based on enabled settings:
Using LDV with the REST API v6
The sender can use the REST API v6 to explicitly grant visibility to documents.
REST API v6 calls ignore all document visibility settings in the UI, as the API call overrides account/group level settings.
The only carry-over behavior is that the sender must specify a document label if it specifies a form field for a particular recipient.