Restrict Moving Job out of Certain Statuses (Protected Statuses)
- Is there a way to restrict a team member from pulling a job out of a status with in the workflow. For example if our simple work flow is lead – contract – permit – production – invoicing. Can we make it so only one person or Access profile can pull job out of the permit status regardless of where they place it (forward / backward / skip ahead). We want to make sure things aren’t being forced ahead until a specific task is completed.
Arnie Lawson
shared this idea
-
Jay Gamero
commented
I cant explain the frustration it causes when someone moves a job out of a status and retriggers automations or it causes it to get lost out of boards
-
Rob Nunziato
commented
YES YES YES - please do this! limiting users from putting jobs or contacts into a status is really only half of the need here.
-
Ashley Cleveland
commented
My team organizes around different job statuses so we can see an accurate representation of the client cycle. A crucial missing feature is protected job status - so that if a job is currently in "Status X" - it can't be moved to any other status unless an Admin access profile moved it to "Status Y"
-
Ashley Cleveland
commented
We have a job status "Complete: Waiting to be Closed" - I would love it if only the admin access profile could change the job status from "Complete: Waiting to be Closed" to anything else. This would mean if the job is in this Complete status, no one else would be able to move the job to any other status.
-
Gabriel Melchor
commented
So this question could be rephrased as having workflow status "gateways" of sorts where they MUST pass through (and be approved) in order to progress to further stages of the workflow?
-
Allen Love
commented
I have the same concern with existing status's with restrictive access permissions. Would be nice that if it was a restricted status only the same access profile can move it.