Shard Group
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
- Transaction Footer
- 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
- Restart agreement workflow
- 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
- CCs
- Recipient Agreement Access
- 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
- Send (Compose) page
- Overview of landmarks and features
- Group selector
- Adding files and templates
- Agreement name
- Global Message
- Completion Deadline
- Reminders
- Password protect the PDF
- Signature type
- Locale for the recipient
- Recipient signature order/flow
- Recipient roles
- Recipient authentication
- Private message for the recipient
- Recipient agreement access
- CC'd parties
- Identity check
- Send an agreement only to yourself
- Send an agreement to others
- Written Signatures
- Recipient signing order
- Send in Bulk
- Send (Compose) page
- 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
- Sandbox
Support and Troubleshooting
Define a signature deadline that automatically cancels the agreement after a defined number of days.
The Completion deadline feature in Acrobat Sign allows senders to set a time limit for recipients to complete their signatures before the agreement is automatically canceled. This helps control signing deadlines, particularly for time-sensitive agreements, such as seasonal contracts or special offers. It also streamlines agreement management by removing old or unlikely-to-complete agreements from the In Progress list, making active agreements easier to track.
Availability:
- Acrobat Standard and Acrobat Pro: Not Supported
- Acrobat Sign Solutions: Supported; Disabled by default
- Acrobat Sign for Government: Supported; Disabled by default
Configuration scope:
The configurable options for this feature can be found here >
The expiration date can be manually set for up to 180 days in the future.
Agreements that don't have an expiration date set automatically expire after 365 days.
The sender experience for Document Expiration will vary depending on if you are configuring a commercial Acrobat Sign Solutions account, or an Acrobat Sign for Government account.
Please select the tier of service you are using from the below options to review the configuration options in their respective environments:
If the Document Expiration feature is disabled, the option in the Agreement settings section of the Compose page will be locked down and uneditable. The note in the Agreement settings summary displays None.
If Document Expiration is enabled with only the default value option turned on, the Completion deadline option is visible on the Compose page in the Agreement settings section. The option displays the deadline date, set to whatever the admin has stored as the default length of time an agreement should remain signable. The date picker to select a new date is greyed out and locked, preventing the sender from editing it.
When the Document Expiration feature is enabled and the option to allow the sender to set the deadline is also turned on, the Completion deadline option is available and editable. The sender is free to enter any number of days (up to 180) that the agreement should remain viable for signature.
- If the option to set the default number of days is enabled, the default date on a new agreement will reflect that default value.
- If the option to set a default date is not enabled, the default expiration value will be 180 days from the sending date.
If the Document Expiration feature is disabled, the option on the Compose page will be absent.
If Document Expiration is enabled with only the default value option turned on, the Completion Deadline option is visible on the Compose page. The option shows as checked to show the deadline is configured, but greyed out, preventing editing by the sender.
When the Document Expiration feature is enabled and the option to allow the sender to set the deadline is also turned on, the Completion Deadline option is available and editable. The sender is free to enter any number of days (up to 180) that the agreement should remain viable for signature.
Expiration timing
Document expiration always occurs during off-peak hours based on the server that sent the agreement. Off-peak hours are 7 PM to 7 AM in the server's local time zone.
By default, agreements sent through the modern Request Signatures process are assigned an expiration time of 11:59 PM, though senders may be allowed to set custom expiration dates and times. However, agreements sent through the API, integrations, or legacy interfaces don't default to 11:59 PM; instead, they adopt the timestamp of when the agreement was initially sent.
If an agreement is set to expire during peak hours, it's queued for expiration but automatically delayed by 12 hours, ensuring the expiration event is processed during off-peak hours.
Status and Editing During Expiration Queuing
- While an agreement is queued for expiration, its status remains In Process on the Manage page and API responses.
- Recipients cannot sign a queued agreement and will receive an error message stating that the agreement cannot be signed.
- During the 12-hour queuing window, the sender can edit the Expiration Date on the Manage page to extend the deadline and allow recipients additional time to sign.
Non-peak hours are from 7 PM to 7 AM based on the most central time zone for the shard group from which the agreement was sent. The time zones used for each shard group are:
|
Time Zone for Peak Hours (7 AM - 7 PM) |
---|---|
NA1, NA2, NA3, NA4 |
America/Chicago |
EU1, EU2 |
Europe/Berlin |
AU1 |
Australia/Sydney |
JP1 |
Asia/Tokyo |
IN1 |
Asia/Kolkata |
SG1 |
Asia/Singapore |
Some shard groups include multiple shards that span multiple time zones. All shards in the group apply the same non-peak expiration window.
For example, the NA1, NA2, NA3, or NA4 all observe the same non-peak hours based on Central Time (GMT -6).
The agreement will expire as scheduled, typically within a few minutes of the set expiration time.
It refers to the shard where the agreement was sent, based on the sender’s environment. (Find out what shard you are on >)
The signer will not be able to sign after the expiration time, even if the agreement has not yet transitioned to EXPIRED status. They will see an error message:
If an agreement has been queued for expiration but the expiration has not yet been processed, the sender may still be able to edit the expiration date. This allows the recipient additional time to sign the agreement before it is expired.
Until the system processes the expiration (within 12 hours), the agreement remains in the IN_PROCESS state. It transitions to EXPIRED once the expiration event is processed.
Yes, you can edit the expiration time at any time until the expiration is processed. There are no restrictions on modifying the expiration time before the agreement transitions to EXPIRED status.
Yes, but the delay may vary by a few minutes depending on the system load.
When setting the expiration date/time on the Request Signatures page, it defaults to 11:59 PM, ensuring the expiration occurs during non-peak hours and is processed at that time or soon after. You can adjust this in the Agreement Settings section.
The agreement will continue to appear as In Progress until the expiration is processed, typically 12 hours later.
Data governance starts only after the agreement transitions to a terminal state (e.g., EXPIRED). A delayed expiration also delays the start of the retention period.
The expiration event is logged once the expiration is processed, which may be delayed by up to 12 hours if the expiration time falls within peak hours.
This update optimizes system performance to accommodate increasing demand.