What's New
Get Started
- Quick start guide for administrators
- Quick start guide for users
- For Developers
- Video tutorial library
- FAQ
- Enterprise Trial
Administer
- Admin Console Overview
- User Management
- Add, edit, and review active users
- Admin Console SSO
- Create function-focused users
- Review users who haven't completed verification
- 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
- Group management
- 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
- PDF/A workflows
- Healthcare customer
- New request signature experience
- New custom workflow experience
- New create template experience
- Account Setup / Branding Settings
- 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
- Apply Adaptive Signature Draw scaling
- Digital Signatures
- Electronic Seals
- Digital Identity
- Report Settings
- Enable classic Reporting
- 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
- Agreement creation experiences
- Require recipient name when sending
- Lock name values for known users
- Allowed recipient roles
- Allow e-Witnesses
- In-person signing config
- Recipient groups
- CCs
- Required fields
- Attaching documents
- Field flattening
- Modify Agreements
- Remove recipients from in-flight agreements
- Agreement name
- Languages
- Private messages
- Allowed signature types
- Reminders
- Signed document password protection
- Send Agreement Notification through
- Signer identification options
- Populate form fields with identity-verified data
- Content Protection
- Enable Notarize transactions
- Document Expiration
- Preview, position signatures, and add fields
- Signing order
- Enable hybrid signature flows
- Add myself
- Send only to internal recipients
- Download agreement link
- Form field borders
- Liquid mode
- Custom workflow controls
- Upload options for the e-sign page
- Post-sign confirmation URL redirect
- Restrict access to shared agreements
- Show Send page after login
- 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
- System Requirements and Limitations
User profile and configurable features
- Address Book
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
- Compose in-person agreement
- Recipient signing order
- Hybrid recipient workflow
- Send in Bulk
- Send (Compose) page
- Authoring fields into documents
- In-app authoring environment
- Automatic field detection
- Drag and drop fields using the authoring environment
- Assign form fields to recipients
- The Prefill role
- Apply fields with a reusable field template
- Transfer fields to a new library template
- Updated authoring environment when sending agreements
- Create forms with text tags
- Create forms using Acrobat (AcroForms)
- Fields
- Field types
- Common field types
- E-signature fields
- Initials field
- Recipient name field
- Recipient email field
- Date of signing field
- Text field
- Date field
- Number field
- Checkbox
- Checkbox group
- Radio button
- Drop-down menu
- Link overlay
- Payment field
- Attachments
- Participation stamp
- Transaction number
- Image
- Company
- Title
- Stamp
- Field content appearance
- Field validations
- Masked fields values
- Setting show/hide conditions
- Calculated fields
- Verified forms
- Field types
- Authoring FAQ
- In-app authoring environment
- Sign Agreements
- Manage Agreements
- Manage page overview
- Copy an Agreement
- 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
- Bulk actions
- Hide multiple agreements
- Digitally sign multiple agreements
- Audit Report
- Reporting and Data exports
Advanced Agreement Capabilities and Workflows
- Webforms
- Reusable Templates (Library templates)
- Manage Shared 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
- Integration keys
Acrobat Sign Developer
- REST APIs
- Webhooks
- Sandbox
Support and Troubleshooting
Build flexible signing flows that keep complex agreements moving without forcing every recipient into the same routing pattern.
Adobe Acrobat Sign lets admins enable hybrid recipient routing so senders can combine ordered and parallel participation in one agreement. Hybrid routing is useful when one part of a process must happen in sequence, but multiple recipients or recipient groups need to act during the same step before the agreement moves forward. Enabling this setting gives senders more flexibility for complex signing flows without requiring a custom workflow for every routing variation.
Before you begin
- Confirm that senders understand the difference between sequential, parallel, and hybrid routing.
- Consider using group-level configuration if only specific teams need to create hybrid workflows.
- For best performance and manageability, plan hybrid workflows with fewer than 50 total participants.
Configuration
Availability
- Acrobat Sign Solutions: Supported
- Acrobat Sign for Government: Supported
- Acrobat Standard and Acrobat Pro: Not supported
Configuration scope
Hybrid recipient routing can be configured at the account and group level.
- Group-level settings override account-level settings.
- Default value: Disabled
Changing this setting will not impact existing agreements that are in-flight.
Access this feature by navigating the administrator's configuration menu to Send Settings > Signing Order
Controls
- Allow senders to specify hybrid routing order — Allows senders to create recipient flows that combine ordered and parallel participation. Hybrid workflows can include individual recipients and recipient groups within the routing sequence.
Hybrid workflows should include fewer than 50 total participants. Count each individual recipient and each member of a recipient group toward the total. Larger hybrid workflows can be harder to manage and may take longer to process, especially if the agreement is modified after it is sent.
How the setting works
When hybrid routing is enabled, senders can create recipient flows that combine ordered and parallel participation. A hybrid flow starts from a sequential routing structure, then allows one or more routing steps to include multiple recipients or recipient groups that act in parallel.
For example, an agreement might use this routing pattern:
- Recipient 1 signs first.
- Recipient 2 signs second.
- Recipients 3, 4, and 5 receive the agreement at the same time and must all complete their actions.
- Recipient 6 receives the agreement after the parallel step is completed.
All recipient steps in a parallel routing step must be completed before the agreement moves to the next routing step. If a parallel step includes a recipient group, the group completes according to the recipient group configuration.
Hybrid workflows can include recipient groups. A recipient group defines who can act within a single recipient step, while hybrid routing defines how recipient steps move through the agreement sequence.
When the setting is disabled, senders cannot create hybrid routing in experiences governed by this setting. They can still use the routing options otherwise allowed by the account or group configuration.
Hybrid routing affects how new agreements are created. Changing the setting does not change agreements that are already in-flight.
Best practices
- Enable hybrid routing only for groups that need mixed sequential and parallel recipient flows.
- Keep hybrid workflows below 50 total participants for best performance and easier troubleshooting.
- Use custom send workflows for repeatable enterprise processes that require consistent routing, approvals, or recipient roles.
- Avoid relying on senders to manually rebuild complex hybrid routing for high-value or regulated workflows.
- Test complex routing with a small internal group before making the configuration broadly available.
- Document when senders should use hybrid routing instead of sequential routing, parallel routing, recipient groups, or custom send workflows.
Related settings
- Recipients will sign in the order they are entered — Sets the default workflow to sequential routing. Hybrid routing builds on ordered recipient routing by allowing one or more routing steps to include parallel participation.
- Allow senders to select signing order — Allows senders to switch an agreement between sequential and parallel routing while composing the agreement. This setting provides routing flexibility but does not replace the hybrid routing control.
- Recipient groups — Allows multiple people to participate in a single recipient step. Recipient groups can be used within hybrid workflows when multiple people need to act during the same step.
- Custom Send Workflows — Lets admins define repeatable agreement workflows with predefined routing, recipients, documents, and sender options.
Things to know / FAQ
- Is the 50 participant guidance a hard system limit?
No. The guidance is a best-practice recommendation for performance and manageability. Keep hybrid workflows below 50 total participants whenever possible. - How should participants be counted?
Count every individual recipient and every member of a recipient group. For example, an agreement with 10 individual recipients and one recipient group with 15 members has 25 total participants. - Why should larger hybrid workflows be avoided?
Larger workflows are harder to review, modify, and troubleshoot. They may also take longer to process, especially if the agreement is modified after it is sent. - Does this setting affect agreements that are already sent?
No. Changing the setting affects whether senders can create hybrid routing for new agreements. It does not change agreements that are already in-flight. - Do all participants in a parallel step need to complete their action?
All recipient steps in the parallel routing step must be completed before the agreement moves forward. If the step contains a recipient group, completion depends on the recipient group configuration. - Can hybrid workflows include recipient groups?
Yes. Hybrid workflows can include recipient groups. Recipient groups define who can act within a single recipient step, while hybrid routing controls how that step is ordered with the rest of the agreement. - Are electronic seals supported in hybrid routing?
No. Electronic seals are not supported in a hybrid signature workflow. - When should admins use Custom Send Workflows instead?
Use Custom Send Workflows when the routing pattern is repeatable, business-critical, or needs to be controlled by admins instead of manually configured by senders.