Configure hybrid recipient routing

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.

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. It 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.