---
key: approve-a-template-change
title: Approve a template change
audience: staff
section: settings/templates
routes: ["/settings/org/templates/approvals"]
permissions: ["work.task_templates.read"]
features: ["settings.org.template-center"]
since: 0.0.1
updated: 0.0.1
status: published
summary: Review a project or task template version someone submitted, approve it, send it back with a comment, or reject it, then publish the approved version so the team can use it.
keywords: [template review, approve template, template approval, request changes, reject template, publish template version, submitted for review, reviewer]
related: [create-a-task-template, create-a-project-template, find-your-templates, review-an-automation-approval]
---

In the sidebar, open **Settings**, then choose **Approval Queue** under **Templates**. The page address is `/settings/org/templates/approvals`. The page title reads **Template approvals**.

Review is optional. An author can publish a template version straight away, or ask for a second look first. This page is where that review happens: a reviewer approves the version or sends it back, and an approved version is then published, from here or from the template itself.

## Before you start

- Your role needs permission to read task templates or project templates to open the page. Approving needs the approve permission for that template type, and publishing needs the publish permission. A greyed-out button tells you which one you are missing when you hover over it.
- The queue only holds versions that were submitted. A draft nobody has submitted is not here; the author presses **Submit** on the version in **Task Templates**. **Project Templates** has no **Submit** button, so project versions only arrive from a connected app.

## Steps

1. Open the **Awaiting my review** tab. Each card shows the template name, whether it is a **Project** or **Task** template, the version number, its status, when it was submitted, and the author's release notes.
2. Press **View detail** to open the template and read the version. Come back when you have seen enough.
3. Type a **Comment** if you have anything to say. A comment is required to request changes or reject.
4. Press one:
   - **Approve** to accept the version as it is.
   - **Request changes** to send it back to the author with your comment. It moves to the **Changes requested** tab.
   - **Reject** to turn it down with your reason.
5. To make an approved version live, find it under **Approved (ready to publish)** and press **Publish**.

## What you see

- The four tabs, **Awaiting my review**, **Changes requested**, **Approved (ready to publish)** and **Submitted by me**, each show a count. **Submitted by me** is where you watch your own submissions.
- **Filter by name** narrows the cards when the queue is long. Type in **Search templates**.
- **Nothing in this queue right now.** means the tab is empty, not that something failed.
- Every action is recorded on the version. On a task template the author sees it under **Review history**.

## If something looks different

- A version you submitted is not under **Awaiting my review**, and **Approve** stays off with a note that only versions awaiting review can be approved: the queue does not pick up submitted versions yet. To put the version live, open the template in **Task Templates**, press **New draft** on that version, then **Publish draft**.
- **Publish** is off with a note that only approved versions can be published: approve it first.
- **Request changes** and **Reject** stay off: type a **Comment** first.
- An approved version you published does not show up for the team: the template itself may be archived. Open it from **View detail** and check its status.

[[route:/settings/org/templates/approvals|Open Approval Queue]]