A client of mine just asked if it’s possible to create a content approval workflow, where editors can create drafts then have other team members approve them so they’re ready to publish. Does anyone have any experience with this sort of thing?
My initial thoughts is that it would require changing the site publishing method from Merge changes immediately to Create a pull request? But how does this work exactly? Would you then create two different sites, one for editors and one for ”approvers”? Perhaps there’s a best practice for this sort of thing?
Really appreciate any pointers you may have, cheers!
If you’re on the Team plan, custom permissions is a great way to do this. You could create two custom permission groups, and set the site:publish:pull-request:merge and site:publish:pull-request:open permissions as appropriate (check out all the available permissions here!)
Maybe you could also to do this by setting up two sites, where one has Editing Locked and publishing enabled but you wouldn’t be able to allow the editors to open pull requests without also allowing them to merge them.
Has anyone else set up a workflow like this, either using these approaches or another way? I’d be interested to hear
Thanks Ryan. I wasn’t aware of publish permissions so this is really helpful.
I tried the two site approach after my initial post and soon realised the issue you’ve highlighted. As they want to prevent editors from publishing content before approval it looks like we’d have to go with the first approach.
but you wouldn’t be able to allow the editors to open pull requests without also allowing them to merge them.