# Campaign Approvals

As Desire scales across teams, regions, and use cases, campaign creation can no longer rely on informal reviews or ad-hoc sign-offs. A structured campaign approvals workflow is essential to ensure brand consistency, compliance, and quality while still enabling speed at scale. It provides clear ownership, traceability of decisions, and confidence that every asset going live has been reviewed by the right stakeholders at the right time. By formalising approvals, Desire reduces rework, prevents costly mistakes, and creates a predictable, auditable process that works equally well for day-to-day BAU campaigns and large-scale, high-impact launches.

&#x20;

Before proceeding, it is recommended that you familiarise yourself with the [Campaign Lifecycle](https://docs.desire.acik.in/basics/campaigns/campaign-lifecycles) that explains the different statuses of a campaign.

&#x20;

Let us look at Campaign Approvals from the lens of (a) The Operator and (b) The Approver.

### Requesting approval

When the operator feels that the campaign has reached a state of maturity and needs approval to proceed, the operator can click on **Send for Approval** option in the **Actions** menu. This opens a popup with a text box for the operator to add an optional message. The operator can then click on **Send for Approval** in the popup to submit the campaign for approval. This immediately notifies all members in the approver group set for the campaign (learn more in [Creating Campaigns](https://docs.desire.acik.in/basics/campaigns/creating-campaigns)).

### Viewing campaigns pending approval

Approvers can know which campaigns are awaiting their approval by clicking on **Approvals** in the left navigation bar. This takes them to a page that lists all campaigns awaiting their inputs. Approvers also get notified via email and in-app notifications.

&#x20;

When the approver opens a campaign awaiting their approval, they can see an **Approve** and **Reject** button against each asset card. Additionally, the operator can see status chips at the top that indicate how many assets are in what status - Approved, Rejected or Pending. The status chips also act like filters, which means clicking on Approved, for example, will show all the assets that have been approved. Clicking on the x button next to the filter removes it and shows all assets.

&#x20;

The operator can review each asset and click on the **Approve** button if everything looks fine. If the approver wants rework or correction in any asset, the **Reject** button allows them to leave a comment. Once the comment is provided, submitting it captures the rejection. There is a **Approve All Pending** button that can approve all assets in the pending status en masse.

&#x20;

Once the asset cards are reviewed, the approver can click on the **Actions** button and click on **Approve** or **Send back to owner**. Only campaigns with no cards needing rework or pending review can be Approved. Even a partially reviewed campaign can be sent back to the owner. Desire will remember which ones were approved and which were pending review. Desire also lets approvers toggle statuses in case of changed mind. A campaign that is approved goes to the **Active** status, while one sent back to the owner goes back to the **Draft** status.

&#x20;

All campaign level messages can be viewed from the **Messages** view available under **Actions**.

&#x20;

&#x20;


---

# Agent Instructions: 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:

```
GET https://docs.desire.acik.in/basics/campaigns/campaign-approvals.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
