Effect of permissions on viewable content in Reviews - Cloud

Review

Security administrators configure permissions. The permissions that apply to reviewer functionality are:

  • Folder Action Permissions, whose users may be configured to view and act upon content in some folders but not in other folders.
    This affects both the book-level and topic-level content, so it's possible for users in a review to see some topics in a book, but not topics inside a permission-denied folder.
  • Release State Permissions, where users may be configured to view content in certain release states but not in others.

What happens when an assigned reviewer does not have permissions to view content

Tex creates a review of book NEWBOOK, which has five topics to be reviewed.

Action 1: Tex assigns Anne as a mandatory reviewer. Anne has permissions to view these five topics and she has permissions to view the selected release state for the review.

  • When Anne opens Reviews she sees NEWBOOK (5) in the Table Of Contents pane, with the five topics listed beneath it.

Action 2: Tex assigns Manny to the same review, but is unaware that Manny does not have permission to the release state for this review.

  • When Manny opens Reviews, there are no topics listed for him. He realizes that something is wrong and phones Tex, who establishes that this is a release state permissions issue.
  • Tex arranges for Manny to be given permission for the appropriate release state, after which Manny is able to see NEWBOOK (5) in the Table Of Contents pane, with the five topics listed beneath it.

Action 3: Tex assigns Reeve to the same review, but Tex is unaware that Reeve lacks folder permissions to view two of the five topics.

  • When Reeve opens the Review, he sees NEWBOOK (3) with three topics listed.
  • He is unaware that Tex had assigned him to review a further two topics.

What if Tex had assigned Reeve as a mandatory reviewer, requiring Reeve to complete his review before the topics can advance to the next release state? Such a configuration would not stop the review process because the software does not consider Reeve as being committed to his two non-viewable topics.

The Table Of Contents (TOC) generated for a given user only includes the items that that user has permissions to see. In Reeve's situation, the software first establishes that Reeve sees only three topic, and then applies the Need To Review requirement to these three topics only.