From 67404dc8ffa4d68fb44f09060dd08c8726e4c918 Mon Sep 17 00:00:00 2001 From: "Dara A." <89842834+daraten@users.noreply.github.com> Date: Mon, 14 Oct 2024 18:03:17 +0100 Subject: [PATCH 1/3] Update esignature-review-sign-requests.md --- microsoft-365/syntex/esignature-review-sign-requests.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/microsoft-365/syntex/esignature-review-sign-requests.md b/microsoft-365/syntex/esignature-review-sign-requests.md index b8b50105278..c7fd6642bde 100644 --- a/microsoft-365/syntex/esignature-review-sign-requests.md +++ b/microsoft-365/syntex/esignature-review-sign-requests.md @@ -130,6 +130,9 @@ When you create a signature request with SharePoint eSignature, it goes through When the status of a request is **Completed**, **Canceled**, or **Declined**, the request can no longer be acted on by either the sender or the recipients. As an example, if a recipient declines a request, the sender would need to send a new request after the reason for declining has been addressed. The original declined request can't be edited. +> [!NOTE] +> For requests sent via other eSignature providers, the status reflected are determined by the signature provider and may differ from the status highlighted above. + ## Access the signed document ### Documents signed with Microsoft SharePoint eSignature All parties involved in the request receive an email notification saying that the request has been completed and the status of the request is **Completed**. In the email, you can select **View signed document** to access the signed document and the request history. Signers can continue to access and download the signed document from the email notification for 30 days after receiving the email. Additionally, request senders will be able to access the originating folder in which the signed document was saved directly from the email. @@ -142,7 +145,7 @@ All parties involved in the request receive an email notification saying that th After all recipients have signed the document, the signatures are added and an audit trail is appended to the signed PDF. Details of the request, including activities and timestamps of when they occurred throughout the signing process, are included. The details include the date and time the request created, date and time when the recipients signed, and so on. These details provide evidence of the integrity of the signing process. The signed document is then digitally signed by a Microsoft certificate to ensure that it can't be tampered with. ### Documents signed with other signature providers -All parties will receive an email notification from the provider when document signing is complete. The email typically contains a link to the signed document or as an attachment. The document is usually accessible via the provider platform and remain there for a period of time permitted by the policy setup on the provider platform. Additionally, a copy of the signed document is automatically stored in SharePoint. The signed document is stored in a provider specific folder within the SharePoint document library of the original document (the original document is the PDF with which the request was initiated from). The signed document can be found using this folder path : **[Document library] > Apps\Signed documents\provider**. For example Contoso Documents → Apps → Signed documents → Docusign. The retention policy of the saved document will inherit the retention policy set up by the SharePoint or tenant admin +All parties will receive an email notification from the provider when document signing is complete. The email typically contains a link to the signed document or as an attachment. Additionally, a copy of the signed document is automatically stored in SharePoint. Once stored, the creator of the request receives an email from SharePoint eSignature with a link to the SharePoint location. The signed document is stored in a provider specific folder within the SharePoint document library of the original document (the original document is the PDF with which the request was initiated from). The signed document can be found using this folder path : **[Document library] > Apps\Signed documents\provider**. For example Contoso Documents → Apps → Signed documents → Docusign. The retention policy of the saved document will inherit the retention policy set up by the SharePoint or tenant admin > [!NOTE] > A copy of the signed document will not be saved if the request is declined or canceled. Any additional document uploaded via the third party platform (i.e. outside of sharePoint) while creating a request will also not be saved back to sharePoint. Only documents initiated from SharePoint are saved back to SharePoint. From b45c1666ebd0e4df6507241a9b427de7b94010a1 Mon Sep 17 00:00:00 2001 From: Chuck Edmonson <33042436+chuckedmonson@users.noreply.github.com> Date: Fri, 25 Oct 2024 09:23:03 -0700 Subject: [PATCH 2/3] Update esignature-review-sign-requests.md --- microsoft-365/syntex/esignature-review-sign-requests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/microsoft-365/syntex/esignature-review-sign-requests.md b/microsoft-365/syntex/esignature-review-sign-requests.md index c7fd6642bde..d2391728627 100644 --- a/microsoft-365/syntex/esignature-review-sign-requests.md +++ b/microsoft-365/syntex/esignature-review-sign-requests.md @@ -131,7 +131,7 @@ When you create a signature request with SharePoint eSignature, it goes through When the status of a request is **Completed**, **Canceled**, or **Declined**, the request can no longer be acted on by either the sender or the recipients. As an example, if a recipient declines a request, the sender would need to send a new request after the reason for declining has been addressed. The original declined request can't be edited. > [!NOTE] -> For requests sent via other eSignature providers, the status reflected are determined by the signature provider and may differ from the status highlighted above. +> For requests sent via other electronic signature providers, the status reflected is determined by the signature provider and might differ from the status described above. ## Access the signed document ### Documents signed with Microsoft SharePoint eSignature From 758a922b04d2361f2e62dba3cc85db88d783fc2d Mon Sep 17 00:00:00 2001 From: Chuck Edmonson <33042436+chuckedmonson@users.noreply.github.com> Date: Fri, 25 Oct 2024 09:25:57 -0700 Subject: [PATCH 3/3] Update esignature-review-sign-requests.md --- microsoft-365/syntex/esignature-review-sign-requests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/microsoft-365/syntex/esignature-review-sign-requests.md b/microsoft-365/syntex/esignature-review-sign-requests.md index d2391728627..1135c625c16 100644 --- a/microsoft-365/syntex/esignature-review-sign-requests.md +++ b/microsoft-365/syntex/esignature-review-sign-requests.md @@ -145,7 +145,7 @@ All parties involved in the request receive an email notification saying that th After all recipients have signed the document, the signatures are added and an audit trail is appended to the signed PDF. Details of the request, including activities and timestamps of when they occurred throughout the signing process, are included. The details include the date and time the request created, date and time when the recipients signed, and so on. These details provide evidence of the integrity of the signing process. The signed document is then digitally signed by a Microsoft certificate to ensure that it can't be tampered with. ### Documents signed with other signature providers -All parties will receive an email notification from the provider when document signing is complete. The email typically contains a link to the signed document or as an attachment. Additionally, a copy of the signed document is automatically stored in SharePoint. Once stored, the creator of the request receives an email from SharePoint eSignature with a link to the SharePoint location. The signed document is stored in a provider specific folder within the SharePoint document library of the original document (the original document is the PDF with which the request was initiated from). The signed document can be found using this folder path : **[Document library] > Apps\Signed documents\provider**. For example Contoso Documents → Apps → Signed documents → Docusign. The retention policy of the saved document will inherit the retention policy set up by the SharePoint or tenant admin +All parties will receive an email notification from the provider when document signing is complete. The email typically contains a link to the signed document or as an attachment. Additionally, a copy of the signed document is automatically stored in SharePoint. Once stored, the creator of the request receives an email from SharePoint eSignature with a link to the SharePoint location. The signed document is stored in a provider specific folder within the SharePoint document library of the original document (the original document is the PDF with which the request was initiated from). The signed document can be found using this folder path : **[Document library] > Apps\Signed documents\provider** (for example, Contoso Documents > Apps > Signed documents > Docusign. The retention policy of the saved document will inherit the retention policy set up by the SharePoint or tenant admin. > [!NOTE] > A copy of the signed document will not be saved if the request is declined or canceled. Any additional document uploaded via the third party platform (i.e. outside of sharePoint) while creating a request will also not be saved back to sharePoint. Only documents initiated from SharePoint are saved back to SharePoint.