We have a few workflow states in our 8.2 instance, including Draft, then Awaiting Content Admin Approval, then Awaiting PAO Approval. Once it's submitted by a contributor level user to the Awaiting Content Admin Approval, the content admin user can submit the item for PAO Approval, or they can edit it.
But if they lock it for edit, it shows up in their own workbox fine under the Awaiting Content Approval workflow state, however when I log in as a PAO user, it's not in the Workbox, and when I navigate to the item in the content editor, it gives me no workflow execution options, only showing that it's locked by the content admin. The PAO user needs to be able to see the item in the workbox and they need to be able to execute workflow commands, even if the item is locked, is that possible?
I've tried giving PAO users workflow state write, workflow state delete, read, write, delete, inherit, etc. access rights to the Awaiting Admin Approval workflow state, but they still don't see the item in their workbox. It seems that locking the item simply removes it from view in the Workbox for all but the user who locked it.
Is there some permission that I'm not giving that would resolve this issue?