{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":50505,"path":"source-to-pay-operations/sourcing-and-procurement-operations/routing-ndas-to-suppliers.md","title":"Routing NDAs to suppliers","bundle":null,"doc_type":null,"release":"australia","body":"\n# Routing NDAs to suppliers\n\nReduce manual effort by providing your procurement specialist with a single place to perform all the necessary actions when creating and routing Non-Disclosure Agreements \\(NDAs\\) to suppliers and third parties.\n\nAs a procurement specialist, you can easily define your NDA content and update signer details with the help of a document template that is provided by default with the Document Template plugin \\[sn\\_doc\\], which is added as a dependency on Procurement Case Management \\[sn\\_spend\\_psd\\]. The signer details are stored in the Signers table.​\n\n**Note:** You must use the November 2023 version of the Document Template plugin \\[sn\\_doc\\] for using the November 2023 versions of the Procurement Case Management and Playbooks for Sourcing and Procurement Operations plugins.\n\nFurther, procurement specialists can easily​ route the NDAs to suppliers and third parties for signing via DocuSign integration, review the signed documents, and close the procurement case of type Send NDA for Signature, from a designated playbook in Source-to-Pay Workspace.\n\nDetails of the workflow are provided here.\n\n1.  Define your NDA content and update the list of participants for signature.​ See [Define NDA content and update the list of signers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/define-nda-content-update-signers.md).\n2.  Set up DocuSign.\n\n    For more information, see [Docusign eSignature Spoke](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/docusign-spoke.md).\n\n3.  Navigate to **All** > **Procurement Case Management** > **Source-to-Pay Workspace**.\n4.  Select the list icon and select **All team work** > **Cases**.\n5.  Select **New**.\n6.  In the Create a new case dialog box, select **Send NDA for Signature**.\n7.  Select **Create Case**.\n\n    **Note:** During a procurement request, when a valid NDA isn’t available for the selected supplier, a procurement case of type Send NDA for Signature is automatically created.\n\n8.  Open the case in Source-to-Pay Workspace, prepare the NDA, and send it for signing to the suppliers and third parties from a playbook.​ See [Send NDA to suppliers for signature](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/prepare-nda-send-to-signers.md).\n\n    **Note:** If the **Playbook** tab isn’t visible in Source-to-Pay Workspace, verify that the Document Template Integration with DocuSign application is installed correctly.\n\n9.  Sign the NDA.\n    -   For external third-party suppliers, [directly sign from the email notification](https://www.youtube.com/watch?v=sFOGy2UwbJk) or from Supplier Collaboration Portal. For more information, see [Using Supplier Collaboration Portal](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/supplier-lifecycle-operations/use-supp-central.md).\n    -   For internal supplier representatives, from Employee Center. For more information, see [Sign a document using DocuSign from Employee Center](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/sign-document-task-ec.md).\n10. Review the signatures from the playbook in Source-to-Pay Workspace, notify the user, and close the case. See [Send NDA to suppliers for signature](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/prepare-nda-send-to-signers.md).\n\n## Additional configurations\n\nYou can make changes to the Send NDA for signature playbook, if you must, from Playbooks.\n\nFor adding new participants, create a new column on the procurement case and update the logic to populate in Playbooks. For more information, refer to the implementation of the signer\\_1 column.\n\nYou can also update the subflows to incorporate any new logic. Flow details can be found in different steps in Playbooks.\n\n-   **[Define NDA content and update the list of signers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/define-nda-content-update-signers.md)**  \nAs a procurement specialist, you can easily define your Non-Disclosure Agreement \\(NDA\\) content and update the list of participants for whose signature is required.\n-   **[Send NDA to suppliers for signature](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/prepare-nda-send-to-signers.md)**  \nAs a procurement specialist, you can use playbooks to prepare a Non-Disclosure Agreement \\(NDA\\) and send it for signing to the suppliers and third parties and review the signed and completed NDA.\n\n**Parent Topic:**[Working with SPO playbooks in the Source-to-Pay Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/work-playbooks-spo.md)\n\n**Related topics**  \n\n\n[Process a purchase order edit in playbook]()\n\n[Process a purchase requisition edit request in playbook]()\n\n[Process a return request in playbook]()\n\n[Process a replacement request in playbook]()\n\n[Process an edit receipt request in playbook]()\n\n[Fulfilling request for copy of contract in playbook]()\n\n[Verifying delivery addresses in playbook]()\n\n[Reviewing and updating general ledger details in playbook]()\n\n[Sourcing intake guided experience with playbooks]()\n\n[Streamlining the supplier risk assessment workflow]()\n\n"}}