Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Sending content for peer review

Updated on January 21, 2021

When you finish your article, share your work with the Tech Doc capability owner so that they can review your content.

  1. In Agile Studio, open the Content Contributor backlog.

  2. In the Content Contributor Backlog, click your user story.

  3. On the user story page, click the Tasks tab.

  4. In the Tasks pane, click the Author article task.

  5. On the task page, in the Actions list, select Change stage.

  6. In the Change stage pane, click Submit.

  7. In the Tasks pane, click the Peer review task.

  8. On the task page, in the Actions list, select Reassign.

  9. In the Assign to list, select Resource, select the capability owner, and then click Submit.

  10. On the Pulse tab, leave a post that the article is ready for review, and tag the capability owner.

Result: When the capability owner completes your review, you receive a Pulse notification that the feedback is ready.
After the capability owner sends you feedback, implement the changes, and then send the doc for editor review.

  • Creating articles

    Share your knowledge and make our client-facing documentation better by adding your content through a user-friendly and intuitive Drupal editor.

  • Sending content for editor review

    After implementing the peer review comments, it is time for a final review by the editing team.

  • Peer review checklist

    Follow best practices for peer reviewing technical documentation content.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us