A user’s role has priority over assignments to content as part of a Team.
For example, a Reviewer can’t author, so if a Reviewer is a member of a Team that is assigned to content For Authoring, the Reviewer will not be assigned, but all Author Team members will be assigned. And Administrators on the same Team are not assigned, because they have authoring access to the content by default.
Here's an overview of how this works for each default role for assigning to content for Authoring and for Reviewing.
Role | Team Assigned as Authors | Team Assigned as Reviewers |
---|
Administrator | Is not assigned, because they have authoring access by default | Is shown as assigned as a Reviewer, but still has editing permission because the role has editing permission by default. Will also find the Project(s) on the For Review menu item on the Browse Projects panel. |
Author | Is assigned as an Author | Is assigned as Reviewer without editing permissions. Will also find the Project(s) on the For Review menu item on the Browse Projects panel, when they select a Project they only have a For Review option. |
Reviewer | Is not assigned (because they have no authoring permission) | Is assigned as Reviewer |
Also, since Reviewers don't have access to any authoring features, if you assign a Team as Owners of a Team the Reviewers won't be assigned.
Comments ( 0 )
Sign in to join the discussion.