I guess it is possible. You can assign Interactor site role to an user. Then, edit the project permissions such that he/she will not be able to publish the content to that project but able to edit workbooks or views.
Hope this helps.
The owner of a content has full control of that content, irrespective of the project settings.
Therefore, if some has published a workbook, then they can update it, even if the project is locked.
So your scenario should be possible
Though you are going to have to move the workbook into the project for the publisher, as they wont be able to publish into the project by themselves (as it will be locked to them)
Hope this makes sense
So sorry Glen- still a little confused. Are you saying the developer would be able to update the content, but (for example) they'd have to publish the new version of their workbook to a "sandbox" folder & would need to rely on an administrator to move the workbook to the "final" project?
A developer would be able to update the content that they own irrespective of the project that the content is in.
However, if a folder is locked to them, and they want to publish a new workbook into it, they wont be able to. In that scenario, they would need to publish to another project, and then an admin would have to move it into the final destination folder.
Hope that clarifies things