> For the complete documentation index, see [llms.txt](https://support.hivo.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.hivo.co/approvals/combined-approval.md).

# Combined Approval

This feature allows users to **combine multiple compatible assets into a single approval request**, helping streamline review processes and ensure consistent feedback across related assets.

### 1. How to create new Combined Approval

#### 🔹 Step 1: Select Assets and Start Approval

* Go to **Library** and select the assets you want to include in the approval.
* Once assets are selected, click the **ACTIONS** button in the top-right corner.
* From the dropdown menu, scroll and select **Start Approval**.

<figure><img src="/files/C9rP9QZvLN6WIw7cx3B4" alt=""><figcaption></figcaption></figure>

In the **Start Approval for Selection** dialog:

* Enable the toggle **“Combine all compatible files into a single approval”.**
* Select the **Approval Template** to apply.

*Note: Only templates you created or those for which you have "Can View/Can Update" permissions will be visible here.*

<figure><img src="/files/H5LnwOpSC6FsomwQJ1Po" alt=""><figcaption></figcaption></figure>

#### 🔹 Step 2: Configure Combined Approval Request

The **Approval Request (Combined)** dialog will appear. You need to:

* **Enter a message** for Reviewers and Approvers.
* **Set the Due Date** for the approval.
* **Assign Owners** for the approval request.

<figure><img src="/files/2Dbvc2od0Zs6nY45MLKB" alt=""><figcaption></figcaption></figure>

#### 🔹 Step 3: Adjust Workflow Stages

Depending on your organization's workflow, you can choose one of the following two configurations to manage user flexibility:

👉 **Option 1: Restricted Mode (Standard Workflow)**

Use this setting if you want to ensure Light Users strictly follow the pre-defined process.

* **User Capability:** Light Users cannot modify the Approval Request structure.
* **Requirement:** Users **must have&#x20;*****"Can View Approval Templates"*** permission.&#x20;

<figure><img src="/files/xOnELr5pFncIzHdoLY5E" alt=""><figcaption></figcaption></figure>

* **Permitted Actions:** They can only enter a **Message and set a Due Date.**
* **Enforcement:** All other settings will follow the designated ***Approval Templates and cannot be changed.***

<figure><img src="/files/TB9sJnQE2hUK1RiYN3FS" alt=""><figcaption></figcaption></figure>

👉 **Option 2: Flexible Mode (Advanced Workflow)**

Use this setting if your organization trusts Light Users to manage the process or when a designated approver might be unavailable and requires a replacement.

* **User Capability:** Light Users can flexibly edit the approval process.
* **Requirement:** You **must grant Light Users the&#x20;*****"Can Create Workflows"*** permission.
* **Warning:** Ensure your organization trusts these users, as they will have the power to delete or change mandatory stages and required approvers.

<figure><img src="/files/1jtJXapjCmGWf4ZpV4rd" alt=""><figcaption></figcaption></figure>

When granted this permission, Light Users can perform the following:

* **Set Information:**
  * Enter a Message for the Reviewer/Approver.
  * Set a Due Date.
  * Add Checklist
* **Flexible Customization (If needed)**: HIVO allows Light Users to tailor the workflow to fit reality:
  * Add/remove Owners.
  * Change or add Approvers/Reviewers for specific stages.
  * Add/remove Stages or add Checklists.
* **Send for Approval:** After click **"Request Approval"** button, the HIVO system will automatically update the status and send notifications to the designated approvers defined in the template.

<figure><img src="/files/AqjzffySNlEimz45KmkQ" alt=""><figcaption></figcaption></figure>

### 2. Manage Combined Approval Requests

👉 Navigate to **Approvals** →  **Combine Approvals** tab to manage approval requests.

⚠️ **User Permission Required:** Users must have **“Can View All Templates”** permission.

#### 🔹 Step 1: Search and Filter Requests

Use filters to quickly locate approval requests:

* **Date Filter (From/To):** Filter by request creation timeframe.
* **Search by Item:** Enter template or asset name.
* **Filter by Status:** Pending, In Review, Approved, or Rejected.
* **Filter by Label:** Categorize by labels (e.g., Content).

<figure><img src="/files/7djR58xlp7hiRecDmXPu" alt=""><figcaption></figcaption></figure>

#### 🔹 Step 2: Review Key Information

Check important columns:

* **Requested:** Shows who created the request and when.
* **Assigned:** Displays all Approvers and Reviewers.
* **Status:** Shows the current stage of the approval process.

#### 🔹 Step 3: Take Action in Approval Workflow

Click the **Item Name** to open the approval workflow. Available actions:

* **Review & Comment:** Add feedback or request revisions.
* **Resolve Comments:** Mark feedback as resolved after updates.
* **Edit Approval:** Modify Owner, Due Date, or assigned Approvers.
* **Change Status:** Manually update approval progress.

This feature helps teams **manage approvals for multiple assets more efficiently**, maintain consistent feedback, and reduce repetitive approval steps.

If you have any questions, feel free to contact support.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.hivo.co/approvals/combined-approval.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.