
Last updated: July 20, 2026
Set up lightweight approval workflows in Quire using custom statuses and Permission Control. Three statuses (Request for Approval, Approved, Rejected) plus role-based Complete permission give you an audit trail on the task itself instead of in email threads. This is the Professional-tier pattern; Premium and Enterprise also have a dedicated Approval feature with built-in actions and categories.
Most approvals at most companies happen in the worst possible place. A Slack DM, a forwarded email, a hallway nod. Three months later when someone asks "who actually approved this?", the answer is buried in a thread nobody can search.
According to governance frameworks like SOX and ISO 27001, decisions need to be recorded against the artifact they apply to, not in a side channel. That audit-trail gap is exactly what those frameworks set out to close. Quire's status-based approval pattern is the lightweight way to close that gap inside your task list, without needing the Premium-tier dedicated Approval feature.
Related: 20 Hidden Quire Features You Should Know — this custom-status approval trick is one of several features power users build for themselves.
Imagine you're steering a project, juggling numerous tasks and deadlines. Your decisions drive the project's success, but ensuring everyone's on board can be a daunting task. That's where the Request for Approval status shines.
With Quire's Request for Approval, you can effortlessly send specific tasks or entire projects to supervisors or stakeholders for their input and approval. It's like having a built-in review process, ensuring everyone's aligned before proceeding. Say goodbye to endless email chains and miscommunication. Request for Approval is your ticket to clarity and accountability.
Once you've dispatched tasks or projects for review, the Approval action lets team supervisors and stakeholders give the green light or offer constructive feedback. It's a straightforward, efficient way to gather input and guarantee satisfaction with project progress.
You might wonder why approvals are worth your attention. Well, let's break it down:

You can add a new status and name it “Request for Approval”. You can set the progress to whatever percentage that you’d like, except 100%.
Then you can create another status and name it “Approved”. Now, set the progress to 100%.
You can also create another status and name it “Rejected” and set a progress percentage to anything but 100%.
To authorize the approval or rejection of a request, you need to configure the permissions for the designated role responsible for this action.
Permission Control is exclusively made for Professional and higher subscription tiers. More information can be found on our Pricing page.
Go to your Organization and choose Edit members in the dropdown menu, scroll down to the bottom of the page, and choose Show all roles in the Permission Control section.

In this permission roles list, you can decide which role can approve the tasks and select the Complete permission and click Save.


Now whenever a member uses the status Request for Approval, the admin or manager can approve the task by changing the status to Approved or Rejected. The team member who requested the approval will also get a notification.

Pick one project that has a sign-off step (marketing asset review, design approval, billing release), create the three statuses, configure Permission Control on the approver role, and run two real approvals through it. The first time you can answer "who approved this, when, on which version" without scrolling Slack, you'll know why the audit trail matters.
Status-based approvals work on Professional and higher Quire plans. For dedicated approve / reject / request-changes actions with approval categories, the Premium plan ships the full Approval feature. Full plan details on the pricing page.
Create three custom statuses, Request for Approval, Approved, and Rejected, with only Approved set to 100 percent progress. Then give the approver role Complete permission through Permission Control.
Custom statuses are the lighter-weight option on Professional and lower plans. The dedicated Approval feature on Premium and higher adds explicit approve, reject, and request-changes actions with a built-in audit trail.
Custom statuses work on every plan including free, but Permission Control, which makes the approval enforceable, needs Professional or higher.
The configured approver gets a notification the moment a task's status changes to Request for Approval. Once they approve or reject it, the requester gets a follow-up notification too.
Email approvals leave no audit trail attached to the work. Quire records the decision on the task itself, with timestamp and approver, so the history stays in one place instead of scattered across threads.