• Article
  • iii minutes to read

Documents that contain sensitive information often require approvals. With the content approving feature in SharePoint, yous can put a simple blessing process for documents in a specific certificate library. Using this content approval process, documents awaiting approval will not be visible to users until they are canonical.

Manage the content approval settings in the library settings page:

Content approval settings

Settings > Versioning settings > Crave content approval for submitted items

Later on this setting is enabled, when users upload documents to this specific library, the document's Approval Status is either in:

  • Draft (if minor and major versions are enabled) or
  • Pending (if only the major version is enabled) state

You can always visit the certificate library to corroborate and refuse documents simply this exercise is tedious. It requires receiving notifications about the awaiting certificate(s), finding the advisable certificate(due south) for approval, then identifying approvers, and finally generating the control to approve/turn down the document(southward).

Alternatively, why not automate this blessing process using a menstruation?

Content approval menstruation in Power Automate

You lot can automate this entire content approval process using an approval flow. When approved, the content approving status of the document is automatically set to Approved; if rejected, the flow sets the content approval status of the document to Rejected.

To set the content approval condition of the document, with the SharePoint connector, utilize the Set content approval condition activity in the flow.

The following actions occur:

  1. Power Automate uses a SharePoint trigger when a new file is added to the library.
  2. Get file metadata provides the ETag belongings (along with many others) required when dealing with content approvals.
    • ETag is a special identifier that identifies the specific version of that detail pending blessing.
  3. Get-go an approval activeness:
    • Include people for approving the documents.
    • Approvers should be either Site Owners or Site Members.
    • If you are managing users in SharePoint groups, make sure approvers are part of the Pattern permission-level group.
  4. If approval response is approved:
    • Prepare content approval condition of the document to Approved.
    • Transport an email to the document author regarding the approving forth with any comments.
  5. If approval response is non approved:
    • Fix content blessing status of the certificate to Rejected.
    • Send an electronic mail to the document author regarding the rejection along with any comments.

Setting up the menstruum in Ability Automate

Using the following template, create a flow in Power Automate.

  1. In the SharePoint library, from the command bar, select Integrate > Ability Automate > Create a flow.
  2. Next, select the template: When a new file is added in SharePoint, complete a custom activeness.

File add custom action

  1. Add the actions equally described in the previous steps.

Flow content approval full

Fix content blessing status action

The content approval action requires the following entries:

  • SharePoint site
  • Library name
  • Identifier of the particular (in this instance, the document ID)
  • Content approval activeness
  • Comments

To meet the ETag, expand Show advanced options.

Annotation

While the content approval action help says that ETag is optional, it is required for documents and pages while it may be optional for list items.

Content approval status Approve

You must ensure you enter the correct site and library name. However, you can go the residue of the values from the previous actions in the flow.

  • Identifier
    • Using the Id property from the trigger output
  • Comments
    • Using the comments holding from the approval response
    • ETAG
  • Using the ETag holding from the Get file metadata action output

Yous tin can now utilise the content approval status action to approve and reject the document based on the blessing response.

The end upshot is that:

  1. After the flow is triggered, approvers get an email to approve/reject the certificate with the document link.
  2. Approvers can now:
    • If your email client supports Outlook-actionable messages: Corroborate it within the electronic mail using actionable messages if your Outlook client supports it.
    • If your email client does non support Outlook-actionable messages: Select Approve or Reject that takes you to Ability Automate site where you lot tin can approve or reject the certificate.
  3. After approving or rejection:
    • Document creator receives an e-mail with the approval status along with the approval comments.

Email approval status

This is an effective fashion to automate document approval in SharePoint using Power Automate! Apply this procedure for list items and pages as well.