---
title: "Approve or reject a request"
url: "https://docs.4hse.com/suppliers/approvals/approve-or-reject"
description: "How a project manager reviews a certificate submitted by a supplier and decides its outcome."
---

# Approve or reject a request

This is the project manager’s side of the workflow. See [Approvals](/suppliers/approvals/) for why the review exists.

## Assign a procedure to the supplier

[Section titled “Assign a procedure to the supplier”](#assign-a-procedure-to-the-supplier)

The workflow starts here: only actions of type **Procedure** can be assigned to a supplier.

![A supplier assigned to a procedure](/_astro/workflow-supplier-manager-1.DKOoqhUn_Z68ntY.webp)

## Receive the request

[Section titled “Receive the request”](#receive-the-request)

When the supplier issues the certificate and links it to the action, the system generates the request and notifies you. The action’s status does not change until the review is complete.

The **Approvals** icon on the desktop opens the list of the requests to handle.

![The Approvals icon on the desktop](/_astro/workflow-supplier-manager-2.DK59LWMG_270d1d.webp)

## Review and decide

[Section titled “Review and decide”](#review-and-decide)

For each request you can review the certificate details and the file uploaded by the supplier. Then:

-   **Accept** — the certificate is validated and the action in the schedule becomes **[Valid](/scheduler-and-notifications/statuses)**. The supplier is notified of the positive outcome.
-   **Reject** — the request is refused. Give the reason in the **notes** field: the supplier receives it with the notification, and has to submit a new request.

This site is protected by reCAPTCHA and the Google [Privacy Policy](https://policies.google.com/privacy) and [Terms of Service](https://policies.google.com/terms) apply.