This project is read-only.

Content Review/Approval Process

Topics: Developer Forum, User Forum
Jul 25, 2008 at 3:31 PM
We currently manage a site for a client that wants to review all changes before they become "live" on the site. Our current process is to use two separate sites - make the content changes on one site and then, when approved, copy the changes over to the live site. This is becoming a very tedious process.

Is there a way to implement an approval process into the system? Preferably, this would be tied into the user management system such that certain user roles could create/edit content and others could approve content, etc.

As a quick stop-gap measure, could we direct users to a specific version of a piece of content (i.e. one that was not published)? We could then make the changes to the content on the live site, save (without publishing) and then send a link directly to the new version of the page for approval.

Jul 27, 2008 at 7:11 PM
At the moment the publishing workflow supports previwing changes (with a link that could be sent for review) but it's not tied to permissions so anyone that can edit can both update a version and publish it. Try expanding the save button and "preview changes".
Jul 29, 2008 at 3:36 AM

You might want to try add in a property that can only be edited by there user group that could be some thing like a Approved check box.

Then you could then override the URL rewriter  to show the newest approved version of the of the item.

hope that helps,