--- title: "Specify Recipient" slug: "specify-recipient" updated: 2026-11-05T19:41:27Z published: 2026-11-05T19:41:27Z canonical: "docs.onespan.com/specify-recipient" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # Specify Recipient The Specify Recipient feature lets you send a transaction even when you don't yet know who the final signers will be. Instead of entering specific people up front, the sender adds placeholder roles and assigns one person as the Recipient Specifier. After the transaction is sent, the Recipient Specifier identifies the real signers, and the signing workflow continues. If you intend to use one of OneSpan's SDKs to use this feature, you must install the latest version of SDKs. To install the latest SDKS see [Downloading SDKS](/v1/docs/downloading-sdks). This feature must also be enabled for your account. To do this, contact our [Support Team](https://www.onespan.com/support). For example: - The sender knows which *roles* must sign, but not the specific individuals. - A coordinator or manager needs to fill in signer details after the transaction is created. The general workflow is as follows: 1. Sender creates a transaction. 2. Sender adds placeholder roles instead of selecting named recipients. 3. Sender designates a "Recipient Specifier". This is the person who will later identify the real signers. 4. The transaction is sent and the system moves into a SENT state. 5. A notification is sent to the Recipient Specifier. 6. The Recipient Specifier enters the actual recipient name/email for one, some, or all placeholder roles. 7. The workflow resumes and the newly designated signers are notified to complete signing. ## Key Concepts | Concept | Description | | --- | --- | | Placeholder Recipient | A required signer role that does not yet have a real person assigned (e.g., "Borrower", "Approver", "Witness"). Uses the PLACEHOLDER signer type. | | Recipient Specifier | The single person responsible for identifying the real recipients for the placeholder roles after the transaction is sent. | | **Specifier Step** | The phase of a transaction lifecycle where the workflow is paused, so that the Recipient Specifier can complete their task. | | **SENT State** | The **OneSpan Sign** transaction status used during the Specifier step. The transaction is marked as SENT, but the signing invites are held back until everything is specified. | | **Specify Recipients Page** | A specific page in the **Signer UI** that the Recipient Specifier uses to fill in the placeholder details and to send the form. | > Only one Recipient Specifier (managing signer) is allowed per transaction. ## Duplicate Signers Specify Recipient supports duplicate signers. If the Recipient Specifier replaces a placeholder role with themselves, and they are already a signer elsewhere in the transaction, the two entries are merged where possible. ## Sending a Specify Recipient Transaction Recipient specification can be performed directly from within the sender interface. If the Recipient Specifier has actions to perform on the transaction's documents and it is their turn to sign, they are taken directly to the signing ceremony after specifying recipients. To send a Specify Recipient transaction: 1. When [Adding Recipients](/v1/docs/configuring-recipients#adding-recipients-to-a-transaction) to a transaction select the recipient who will be the Recipient Specifier. This is the person will identify the actual signers for the transaction. Add them to the transaction as you would a regular signer. 2. Click the ellipsis beside this recipient (...) and then click **Advanced Settings**. ![Menu recipient options for editing details, settings, and managing attachments in an application.](https://cdn.document360.io/038f59a7-abd0-4c14-9de7-3434d28b49fd/Images/Documentation/OSS_Recipient%20Advanced%20Settings.png?sv=2026-02-06&spr=https&st=2026-11-08T23%3A39%3A56Z&se=2026-11-09T00%3A39%3A56Z&sr=c&sp=r&sig=8E79KswaLUzNfyCulRJ%2BhJ4RE%2BTQAw4rjz4DICnNrkI%3D) 3. Toggle the **Specify placeholder recipients** option and click **Save.** ![](https://cdn.document360.io/038f59a7-abd0-4c14-9de7-3434d28b49fd/Images/Documentation/Specify%20Recipient.png?sv=2026-02-06&spr=https&st=2026-11-08T23%3A39%3A56Z&se=2026-11-09T00%3A39%3A56Z&sr=c&sp=r&sig=8E79KswaLUzNfyCulRJ%2BhJ4RE%2BTQAw4rjz4DICnNrkI%3D) 4. Add as many **Placeholder** recipients as you need. To do this, add a recipient, enter a **Placeholder Name**, and then click the recipient icon ![](https://cdn.document360.io/038f59a7-abd0-4c14-9de7-3434d28b49fd/Images/Documentation/recipient_icon.png?sv=2026-02-06&spr=https&st=2026-11-08T23%3A39%3A56Z&se=2026-11-09T00%3A39%3A56Z&sr=c&sp=r&sig=8E79KswaLUzNfyCulRJ%2BhJ4RE%2BTQAw4rjz4DICnNrkI%3D) to the left of their name. From there, select **Placeholder** as the recipient type. ![User interface displaying options for recipient, group, and placeholder selections.](https://cdn.document360.io/038f59a7-abd0-4c14-9de7-3434d28b49fd/Images/Documentation/Specify%20Recipient_Placeholder.png?sv=2026-02-06&spr=https&st=2026-11-08T23%3A39%3A56Z&se=2026-11-09T00%3A39%3A56Z&sr=c&sp=r&sig=8E79KswaLUzNfyCulRJ%2BhJ4RE%2BTQAw4rjz4DICnNrkI%3D) 5. Continue editing your transaction as per usual (documents, signature fields, etc.) and then send the transaction for signing. 6. Once the designated **Recipient Specifier** receives the transaction, they will then be responsible for providing the actual recipient's information for each **Placeholder**. These signers will then be directed to the signing ceremony. ![](https://cdn.document360.io/038f59a7-abd0-4c14-9de7-3434d28b49fd/Images/Documentation/Specify%20Recipient_Specifier.png?sv=2026-02-06&spr=https&st=2026-11-08T23%3A39%3A56Z&se=2026-11-09T00%3A39%3A56Z&sr=c&sp=r&sig=8E79KswaLUzNfyCulRJ%2BhJ4RE%2BTQAw4rjz4DICnNrkI%3D) Recipient specifiers can replace a placeholder with themselves by clicking **This is me** in the placeholder's action menu (the ellipses beside the signer’s name) . Their name, email, and other details are filled in automatically, and the placeholder's authentication method is replaced with the specifier's own. A confirmation message appears before the replacement is applied and warns if an existing authentication method will be replaced. Once confirmed, the placeholder's original details and authentication method can't be restored. ## Previewing Documents Before Specification Before completing specification, the Recipient Specifier can preview the transaction's documents to confirm exactly which signatures and fields belong to each placeholder, rather than assigning recipients based on role name alone. Only placeholder fields are shown — fields belonging to named recipients (senders, regular signers) do not appear in any preview mode. | Mode | Description | | --- | --- | | All placeholders | Displays every transaction document with the signatures and fields of all placeholders needing specification. Fields are color-coded using the same placeholder color scheme described under Placeholder List Display. | | Single placeholder | A "Preview as recipient" option next to each placeholder opens a modal scoped to only the documents on which that placeholder has signatures or fields. | | Thumbnail | Clicking a document thumbnail opens a full-page preview, auto-scrolled to the relevant page, with the ability to scroll up or down through the remaining documents from within the same view. | ### Submitting a Recipient Clicking **Submit recipients** displays the following confirmation dialog: *"Submitting the form will perform all replacements, remove any unidentified recipients, and initiate the transaction signing. Once submitted, you will no longer be able to make any changes to the recipients. Do you want to continue?"* - **Confirm**: Performs the placeholder replacements, removes any remaining unspecified placeholders, and sends the transaction for signing. - **Cancel**: Returns to the Specify Recipients page without changes. ### Auto-Submit on Last Placeholder Deletion If the specifier deletes the last remaining placeholder and no other recipients require specification, the form is auto-submitted. The confirmation message reads: *"This action will permanently remove the recipient from the transaction and auto-submit the form. Do you want to continue?"* ## Disputing a Recipient Specification In addition to completing specification, the Recipient Specifier can dispute (decline) the request instead — returning the transaction to the sender with a reason, rather than leaving it stalled or attempting to specify recipients incorrectly. To dispute a recipient specification request: 1. From the Specify Recipients page, open **More Actions**. 2. Select **Dispute**. 3. In the "Dispute Recipient Specification" panel, enter a reason in the required **Enter a reason** field. The **Dispute** button is disabled until a reason is entered. 4. Select **Dispute** to submit, or **Cancel** to return to the Specify Recipients page without disputing. Disputing a recipient specification has the following effects: | Element | Value | | --- | --- | | Transaction status | Set to Draft (Declined). | | Specifier confirmation page | Title: "Recipient Specification Disputed." Body: "You have disputed the recipient specification for this transaction. An email notification has been sent to the transaction sender." | | Handover URL | Not followed on dispute, even if one is configured. | | Dashboard indicator | An "i" icon appears next to the transaction name in the Drafts folder. Tooltip: "This transaction has been disputed." | | Transaction Edit page | Displays "Please review the details of '{transaction name}' cancellation," with the dispute reason included in the "Cancellation Details for {transaction name}" modal. | | Re-accessing the specifier/signing link | Displays an error page. Title: "Transaction Disputed." Body: "This transaction is no longer available as it has been disputed. Please contact the transaction sender for further information." |