Publishing for Review

This article details protocols for publishing modules to Review 360 and configuring access for internal/client reviews.

Core Publishing Process

1. Publish to Review 360
2. Email link to TK reviewer
3. Republish updates as "new version to existing item"

Configuration Requirements

Internal TK Review

• Menu: Restricted navigation

• Final assessment: Draw randomly

  ⚠️ Conflicting guidance note: See "Final Assessment Settings for Review" for testing requirements of all questions

Client Review

• Menu: Free navigation
• Final assessment: Show all questions

RME Upload Protocols

Labels & Access

• Apply version labels (e.g., ALPHA/BETA)
• Enable Share Comments
• SMS projects: Activate Require Login
• Reporting projects: Use public invite

Roles & Permissions

1. Add Paula as:
   • Reviewer (send email via RME)
   • Developer (no email)
2. Add SME as:
   • Reviewer (no email)
   • Developer only for SMS projects (no email)

Version Control

• Maintain same Review 360 item across iterations
• Preserve comment history between versions

Notifications

• Never send RME emails when adding developers
• Manual email required for Paula's reviewer access