Restrict Status based on permissions
Log In
Caroline Ginty
Merged in a post:
Limit Task Status Changes by User or Role
Riley Dickerson
Currently, any user with edit access to a task can change its status to any available option. For better workflow control and accountability, it would be extremely helpful to restrict which users or roles can move tasks to specific statuses.
For example, I want my team to be able to move tickets from “To Do” to “In Progress,” but only managers or leads should be able to move tickets to “Closed” or “Done.” This would prevent tasks from being closed prematurely and ensure proper review and approval before completion.
This would allow admins to set permissions for which users or roles can move tasks to specific statuses. For even more granularity, it would be great if we could allow status change restrictions to be set at the Space, Folder, or List level, and Ideally provide an override option for workspace owners/admins.
This feature would improve quality control, accountability, and process compliance for teams that require strict review or approval steps before closing tasks. This would complement the Approvals custom field and advanced permissions, but provide more granular control over workflow transitions.
T
Tomáš Brokeš
yes this is must have
Taras Kozak
In ideal world it could be an Advanced section in Statuses Modal to set all legal transition bi-directional graph (to excluse illegal arrows from all-to-all connection/direction) and required permission to do legal transition between statuses (who can change status for every arrow).
In this case you can block transition from "DEVELOPMENT" to "PRODUCTION" status skipping "TESTING" one.
T
Test
I also need this
T
Tim Muller
Need this.
Beth Tidwell
Agreed! Would be very useful.
A
Avrumi Eisner
This would be very helpfull. Including guests users.
Johan Dahlqvist
Longing for this..!
Muhammad Jamil
I'm surprised that 5 years since requested, and this is still not done. All the major ClickUp competitors are offering this now so this should be prioritized.
Diogo Luiz Miranda
This is a must-have, to have any real control over workflows. We have a use case, for purchasing, where there's a need for approval before purchase. If we can restrict the "Approved" status to a specific user or group, that will enable us to "control" who can approve or move something.
Load More
→