Use Digital Identity Gateway with Send in Bulk - New

Require Send in Bulk recipients to verify their identity using a configured Digital Identity Gateway provider.

Digital Identity Gateway (DIG) can be applied to Send in Bulk recipients during authoring or assigned to individual recipients through CSV. Use authoring when recipients can share the same authentication configuration. Use CSV when authentication or identity-check requirements need to vary by recipient or child agreement.

Each generated agreement uses the existing Digital Identity Gateway authentication and audit process.

Before you begin

Before using Digital Identity Gateway with Send in Bulk:

• Digital Identity Gateway must be enabled for the sending account or group.
• At least one Digital Identity provider must be configured and available to the sender.
• The sender must have access to Send in Bulk.
• Use the current Send in Bulk CSV format when assigning DIG through CSV.

For provider configuration, see Digital Identity Gateway.

Choose how to apply Digital Identity Gateway

You can apply DIG in two ways:

• During Send in Bulk authoring — Use this when recipients can use the same authentication configuration.
• Through CSV — Use this when individual recipients need different authentication methods, providers, or email-matching requirements.

Limitations

• Digital Identity Gateway must already be configured and available to the sender.
• The provider specified through CSV must be enabled for the sending account or group.
• Name matching and partial name matching aren't currently supported through Send in Bulk CSV.
• Send in Bulk CSV supports email matching only for recipients using Digital Identity Gateway.
• Digital Identity Gateway support applies to the current Send in Bulk experience and doesn't add DIG support to the legacy /megaSigns API.

Apply Digital Identity Gateway during authoring

Acrobat Sign applies the selected Digital Identity provider to the generated child agreements.

Recipients must successfully authenticate with the selected provider before they can access the agreement.

Apply Digital Identity Gateway through CSV

Use CSV when authentication needs to vary between recipients or child agreements.

For each recipient who must use DIG:

• Set Recipient_X:Auth_Type to DIG_ID.
• Set Recipient_X:Auth_Value to the provider ID.

Replace X with the recipient number.

For example:

The provider must already be enabled for the sending account or group.

The provider ID can be obtained from the identity provider or Adobe Support.

For complete CSV syntax and supported authentication values, see Create a CSV file for Send in Bulk.

Mix authentication methods

CSV configuration is applied per recipient.

Recipients in the same Send in Bulk transaction can use different authentication methods, provided those methods are available to the sending group.

For example, one recipient can use Digital Identity Gateway while another uses a different supported authentication method.

Apply email matching through CSV

For recipients using DIG_ID, CSV can also define whether the authenticated identity must satisfy email matching.

Per-recipient options include:

• Requiring email matching.
• Allowing custom alternate email addresses.
• Allowing alternate email addresses already registered with the authenticated identity.
• Supplying custom alternate email addresses that can satisfy the match.

These options are applied independently to each DIG recipient.

For the complete CSV field names, formatting, and examples, see Create a CSV file for Send in Bulk.

For information about email-matching policy and alternate identities, see Configure an Identity Check Policy for digital identities.

Use custom alternate email addresses

When multiple custom alternate email addresses are supplied through CSV, enter them as a comma-separated list enclosed in quotation marks.

For example:

"alternate1@example.com,alternate2@example.com"

The quotation marks prevent the commas between addresses from being interpreted as CSV column separators.

How authentication applies to child agreements

Each Send in Bulk child agreement is independent.

When DIG is applied to a recipient:

• The recipient must authenticate with the configured identity provider before accessing the agreement.
• Any configured email-matching requirements apply to that recipient.
• Authentication activity is recorded with the child agreement's audit history.
• Authentication in one child agreement doesn't affect other child agreements in the bulk send.

The sender can monitor the generated agreements from the Send in Bulk parent transaction on the Manage page.

Recipient experience

Recipients use the standard Digital Identity Gateway authentication flow.

When a recipient opens the agreement:

1. Acrobat Sign indicates that identity verification is required.
2. The recipient continues to the configured identity provider.
3. The recipient completes the provider's verification process.
4. After successful verification, the recipient returns to Acrobat Sign.
5. The recipient can access and complete the agreement.

The exact verification experience depends on the selected identity provider.

For more information about recipient authentication, see Digital Identity Gateway.