Skip to content

Commit 7715f7e

Browse files
Merge pull request #28513 from MicrosoftDocs/chucked-working
Update esignature-review-sign-requests.md
2 parents 7226733 + a6e0def commit 7715f7e

1 file changed

Lines changed: 9 additions & 4 deletions

File tree

microsoft-365/syntex/esignature-review-sign-requests.md

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ ms.author: chucked
44
author: chuckedmonson
55
manager: jtremper
66
ms.reviewer: amcdonnell
7-
ms.date: 05/06/2025
7+
ms.date: 05/19/2025
88
audience: enabler
99
ms.topic: how-to
1010
ms.service: microsoft-syntex
@@ -134,8 +134,12 @@ When the status of a request is **Completed**, **Canceled**, or **Declined**, th
134134
> 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.
135135
136136
## Access the signed document
137+
137138
### Documents signed with Microsoft SharePoint eSignature
138-
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. The file name of the signed document will be the original file name with "signed" and the date and time appended to it.
139+
140+
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.
141+
142+
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. The file name of the signed document will be the original file name with "signed" and the date and time appended to it.
139143

140144
> [!NOTE]
141145
> When you open a PDF document on a SharePoint site, you won't see the details of the request if your default PDF viewer is set to Adobe. You'll need to set PDF viewer as your default viewer.
@@ -145,7 +149,8 @@ All parties involved in the request receive an email notification saying that th
145149
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.
146150

147151
### Documents signed with other signature providers
148-
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.
152+
153+
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.
149154

150155
> [!NOTE]
151-
> 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.
156+
> A copy of the signed document will not be saved if the request is declined or canceled. Any additional document uploaded via a provider 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.

0 commit comments

Comments
 (0)