Does your documentation process call for several people to contribute to the development of content? Maybe you are working to manually manage multiple levels of review and approval. Many policyIQ users are aware that they can enforce the review process by utilizing the formal Approval capability—established in the policyIQ Setup module on each Template. We can see, however, that many organizations are not utilizing the Editors property on Pages to further manage their hierarchy of contributors and reviewers. 
 
In many policyIQ sites, we see that the Editors on a Page are the same as the Administrators, illustrating that they have not been adjusted to represent a different set of users.

Let’s be sure that you are aware of the differences between the Administrators and Editors of items: Administrators are able to edit all properties of an item, while Editors may only change the Viewers property and any Template fields.

Editors are not able to Publish an item.

So, what this means is that you can designate a group as Editors to work on a Page. The Editors can give their 2 cents and represent the perspective of the hands-on operator of the task or procedure. You don’t have to worry about line staff publishing unauthorized content. Next, an Editor will “check in” the Page which can be auto-routed back to their manager or an Administrator of the Page. The Administrator can then make any final adjustments to the content and review the Page prior to choosing the Publish option which sends the Page on to the director or Approver for final review.

Can you see a possible application of adding this additional level of contributors to your content development? Are you still partly cloudy on how to implement this property in your process? Contact us and let us know what you’re trying to accomplish and we’ll guide you toward the workflow options in policyIQ that will best support your development, review and approval process.