Navigate to Account Settings > Electronic Seals.
What's New
Get Started
- Quick start guide for administrators
- Quick start guide for users
- For Developers
- Video tutorial library
- FAQ
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
- Edit a user's group membership through the group interface
- 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
- Account tier and ID
- New Recipient Experience
- Self Signing Workflows
- Send in Bulk
- Web Forms
- Custom Send Workflows
- 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
- Delegation for users in my account
- Allow external recipients to delegate
- Authority to sign
- Authority to send
- Power to add Electronic Seals
- Set a default time zone
- Set a default date format
- Users in Multiple Groups (UMG)
- Group Administrator Permissions
- Replace recipient
- Audit Report
- In Product Messaging and Guidance
- Accessible PDFs
- New authoring experience
- Healthcare customer
- Account Setup
- Add logo
- Customize company Hostname/URL
- Add company name
- Post agreement URL redirect
- Signature Preferences
- Well formatted signatures
- Allow recipients to sign by
- Signers can change their name
- Allow recipients to use their saved signature
- Custom Terms of Use and Consumer Disclosure
- Navigate recipients through form fields
- Decline to sign
- Allow Stamps workflows
- Require signers to provide their Title or Company
- Allow signers to print and place a written signature
- Show messages when e-signing
- Require signers to use a mobile device to create their signature
- Request IP address from signers
- Exclude company name and title from participation stamps
- Digital Signatures
- Electronic Seals
- Digital Identity
- Report Settings
- New report experience
- Classic report settings
- Security Settings
- Single Sign-on settings
- Remember-me settings
- Login password policy
- Login password strength
- Web session duration
- PDF encryption type
- API
- User and group info access
- Allowed IP Ranges
- Account Sharing
- Account sharing permissions
- Agreement sharing controls
- Signer identity verification
- Agreement signing password
- Document password strength
- Block signers by Geolocation
- Phone Authentication
- Knowledge-Based Authentication (KBA)
- Allow page extraction
- Document link expiration
- Upload a client certificate for webhooks/callbacks
- Timestamp
- Send settings
- Show Send page after login
- Require recipient name when sending
- Lock name values for known users
- Allowed recipient roles
- Allow e-Witnesses
- Recipient groups
- Required fields
- Attaching documents
- Field flattening
- Modify Agreements
- Agreement name
- Languages
- Private messages
- Allowed signature types
- Reminders
- Signed document password protection
- Send Agreement Notification through
- Signer identification options
- Content Protection
- Enable Notarize transactions
- Document Expiration
- Preview, position signatures, and add fields
- Signing order
- Liquid mode
- Custom workflow controls
- Upload options for the e-sign page
- Post-sign confirmation URL redirect
- Message Templates
- Bio-Pharma Settings
- Workflow Integration
- Notarization Settings
- Payments Integration
- Signer Messaging
- SAML Settings
- SAML Configuration
- Install Microsoft Active Directory Federation Service
- Install Okta
- Install OneLogin
- Install Oracle Identity Federation
- SAML Configuration
- 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
- Download Agreements in Bulk
- 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
- Restart the agreement
- 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
- Manage Agreements
- Manage page overview
- Delegate agreements
- Replace Recipients
- Limit Document Visibility
- Cancel an Agreement
- Create new reminders
- Review reminders
- Cancel a reminder
- Access Power Automate flows
- More Actions...
- How search works
- View an agreement
- Create a template from an agreement
- Hide/Unhide agreements from view
- Upload a signed agreement
- Modify a sent agreement's files and fields
- Edit a recipient's authentication method
- Add or modify an expiration date
- Add a Note to the agreement
- Share an individual agreement
- Unshare an agreement
- Download an individual agreement
- Download the individual files of an agreement
- Download the Audit Report of an agreement
- Download the field content of an agreement
- Audit Report
- Reporting and Data exports
- Overview
- Grant users access to reporting
- Report charts
- Data Exports
- Rename a report/export
- Duplicate a report/export
- Schedule a report/export
- Delete a report/export
- Check Transaction Usage
Advanced Agreement Capabilities and Workflows
- Webforms
- Reusable Templates (Library 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
- Save completed web form documents to SharePoint Library
- Save completed web form documents to OneDrive for Business
- Save completed documents to Google Drive
- Save completed web form documents to Box
- Agreement data extraction
- Agreement notifications
- Send custom email notifications with your agreement contents and signed agreement
- Get your Adobe Acrobat Sign notifications in a Teams Channel
- Get your Adobe Acrobat Sign notifications in Slack
- Get your Adobe Acrobat Sign notifications in Webex
- Agreement generation
- Generate document from Power App form and Word template, send for signature
- Generate agreement from Word template in OneDrive, and get signature
- Generate agreement for selected Excel row, send for review and signature
- Custom Send workflows
- Share users and agreements
Integrate with other products
- Acrobat Sign integrations overview
- 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
Overview
Electronic seals (e-seals) provide the same legal validity as a company rubber stamp on paper, where no individual signer authenticity is conveyed. The main difference between a seal and a signature is that a signature is meant for individuals (natural persons), whereas a seal is used by a legal entity (business or organization). E-seals can be applied by more than one person or system under the control or supervision of the legal entity.
The electronic sealing feature in Adobe Acrobat Sign allows organizations to apply e-seals using digital certificates issued to their legal entity to help convey the integrity and authenticity of invoices, statements, or other official documents. Seals can be placed using only a graphic, a text block containing the subject, reason, date, and time of the seal, or a combination of both the graphical seal and text.
Users are assigned specific privileges to automatically apply an e-seal for their organization to a document using a digital certificate obtained from a Trust Service Provider (TSP) with a Cloud Signature Consortium (CSC) API integration with OAuth 2.0 Client Credential authorization flow. The following providers currently support this feature:
Prerequisites
- An enterprise-tier account is required to access the API and configure the seal.
- Acquire the following from your Trust Service Provider (see above for TSP options)
- OAuth 2.0 client_id and client_secret: Adobe uses these values to generate an access token which is used to make remote signing calls to the TSP. The access token is generated by calling the oauth2/token endpoint with a grant_type of "client_credentials." Please see section 8.3.3 of https://cloudsignatureconsortium.org/wp-content/uploads/2020/01/CSC_API_V1_1.0.4.0.pdf for details.
- Credential ID: An Identifier associated with the credentials of a given user for the TSP provider. A credential is a cryptographic object with related data used to support a remote digital signature over the Internet. It consists of the combination of a public/private key pair (also named "signing key" in CEN EN 419 241-1 [i.5]) and an X.509 public-key certificate managed by a remote signing service provider on behalf of a user. The credential is used as the entity with which the electronic seal is associated.
- Credential PIN: A pin code is used to secure access to a given TSP credential.
Configuration
Availability:
Electronic Seals are available for enterprise license plans.
Configuration scope:
The feature can be enabled at the account and group levels.
The controls for this feature can be assessed by navigating to the Electronic Seals tab of the admin menu
Three settings must be configured to expose the e-seal options on the user's Send page.
- Allow electronic seals as a recipient role.
- Enable the account/group for senders to mark recipients with an electronic sealer role.
- Authorize user(s) to add electronic seals to their agreements, either by the account/group level setting or individually through the user's profile.
To allow your senders to use the e-seal role, you must enable it in the group from which the agreement will be sent.
- Enable the role at the account level and allow the group's default inheritance of the setting.
- Explicitly enable the role in the individual group's settings.
To enable the electronic seal recipient role, navigate to: Account Settings > Send Settings > Allowed Recipient Roles
If the option to allow electronic sealers is not enabled for the group in which the agreement is configured, the Add Electronic Seal link will not be exposed.
The default status for users to include e-seals in their agreements can be configured at the account and group levels.
For most accounts, the recommendation is to disable access at the account level and explicitly enable groups where appropriate. Accounts that have Users in Multiple Groups enabled may find dedicated groups for agreements that demand e-seals useful in limiting e-seal access at the group level.
The options are:
- By default, anyone in the group can use e-seals.
- By default, no one in the group can use e-seals.
In either case, individual users can be explicitly configured to override the group-level settings. (See Authorize individual users to add electronic seals below.)
If the option to add electronic seals is not enabled for the user creating the agreement, the Add Electronic Seal link will not be exposed.
Account-level administrators can edit the user profile of individual users to explicitly enable/disable their authority to include electronic seals in their agreements.
This authority is applied to the user directly, which overrides the group level settings for all groups in which the user is a member.
It is recommended that user-level enablement only be done when the expectation is that the whole of the account will have access to e-seals disabled, and only specialized userIDs will initiate agreements that exploit e-seals (such as API-driven workflows/technical accounts).
To explicitly enable/disable access to apply e-seals:
- Navigate to Users > [individual user] > Edit User Detail.
- Select/deselect the User can electronically seal documents checkbox.
- Save the user profile.
Create a new e-seal
At least one e-seal must be configured, active, and available to the group from which the agreement is being sent. Otherwise, the option to add the e-seal isn't exposed on the page.
Creating an e-seal requires that you first obtain a digital certificate from a TSP with a CSC API integration. (See the Prerequisites)
Once you have the certificate, you can configure the e-seal:
-
-
Click the plus icon with a circle around it .
-
The interface to configure the new e-seal opens.
Enter the e-seal parameters using the information provided by your TSP:
- Name - Enter an intuitive name for the e-seal. This name is presented to the senders on the Send page.
- Cloud Signature Provider - Select the provider that issued the certificate.
- OAuth Client ID - Enter the client ID obtained from your TSP.
- OAuth Client Secret - Enter the client secret obtained from your TSP.
- Credential ID - Enter the credential ID obtained from your TSP.
- Credential PIN - Enter the credential PIN obtained from your TSP.
- Reason - Provide some text that identifies the reason for the e-seal application. This string is displayed in the e-seal on the document and in the audit report.
- Group -Select the group for which the e-seal is available.
- Graphic appearance - One or both of the blow options must be enabled for the seal to be successfully saved and used:
- Display Subject, Reason, Date, Time and Acrobat logo - When enabled, the text components of the seal are applied in the signature. If not enabled, only the seal graphic is used.
- Upload a graphic file to customize the appearance of this Seal - When an image is uploaded, it is applied to the signature. If no image is uploaded, only the text is used.
- Display Subject, Reason, Date, Time and Acrobat logo - When enabled, the text components of the seal are applied in the signature. If not enabled, only the seal graphic is used.
- Display email - Provide an email address that should be associated with the e-seal. This email is displayed in the email template as the address for the e-seal recipient.
-
Select Save when done.
The configured e-seal is created in Active status and displays on the Electronic Seals page in the list of seals.
The e-seal is ready to be applied to agreements immediately.
Things to know
Electronic Seals cannot be added to Recipient Groups.
Electronic Seals cannot be added to Hybrid signature flows.