Page Permissions with Workflow
Permalink Browser Info Environment
We adding some workflow to our site that will use this addon, is there anything I should be aware of? Basically multiple users that have permissions to post content to various parts of the site, but with an editor that needs to approve the publishing of those posts.
| Type: | Discussion |
|---|---|
| Status: | New |
It's definately a nice piece of work! I've been using a couple licenses for some time now and love it's flexibility. If you get stuck setting up the permissions, as there seems to be a couple ways to do it, I'd be happy to help you out, or throw you screenshots of my setup to guide you!
There's nothing inherent to this package that would affect the permissions for workflows. It's the same as using the built in composer feature with workflows. If a page needs one before publishing, then it is applied.
Some people have asked for workflow approvals to be worked into the list view, but it's a bit beyond what I have time to do with the package, especially with 5.7 coming down the pipe.
There are some considerations, for sure. But they're more built into workflows than this package. For instance, if you have workflows enabled and someone publishes version 2, then someone else publishes version 3, but neither are approved, whichever one is approved later wipes out changes from the other user.
I'm currently using it on a site with 100s of editors with some pretty advanced permissions on where each group can publish, and what workflows are triggered when new pages are added. It hasn't seemed to break anything...
Some people have asked for workflow approvals to be worked into the list view, but it's a bit beyond what I have time to do with the package, especially with 5.7 coming down the pipe.
There are some considerations, for sure. But they're more built into workflows than this package. For instance, if you have workflows enabled and someone publishes version 2, then someone else publishes version 3, but neither are approved, whichever one is approved later wipes out changes from the other user.
I'm currently using it on a site with 100s of editors with some pretty advanced permissions on where each group can publish, and what workflows are triggered when new pages are added. It hasn't seemed to break anything...