In this article:
Permission Filters and Hierarchy of Privileges
New installations of REVIEW are pre-configured with permission settings based on best practices.The Administrator user role has global access (full privileges) to all REVIEW functionality. Privileges cannot be downgraded for Administrator's.
For other user roles, making changes to the default settings are necessary for view, edit, update and delete privileges of projects, documents and versions, plan review assignments and reviewer comments.
The hierarchy of the Permission filters are shown in the diagram, right.
Permission Filter Definitions
Global access
This is the least restrictive permission filter. It provides access to data records not dependent on Project team membership. The Administrator user role is granted global access privileges throughout the application.
Project member
Provides access to Projects based on Project team membership. Users who create new projects are automatically made project team members.
Group member
This filter provides access based on project membership and group membership.
- For users who conduct plan review, the Assignments Page is preconfigured to display unfinished assignments based on project team membership and group membership.
- Individuals in the Group Manager role typically require edit and delete rights to manage comments, stamps and sketches for staff members within their Group(s).
Own(er)
This is the most restrictive permission filter. It provides access to data records created by the individual, personally.
User Role Definitions
User roles cannot be renamed, however, adjusting the permissions for each user roles is supported.
| User Role | Description |
|---|---|
| Admin | Responsible for user accounts, permissions and configuration. |
| Project Coordinator | This user typically coordinates many projects for one or more Managers. This user may also be granted permissions to manage configurations, perform Intake and |
| Project Manager | This user typically manages their own Projects. |
| Group Manager | This user manages plan reviewers in his Group(s) and may be granted permissions to edit/delete markups for users in his Group(s). |
| Reviewer | This individual conducts plan reviews and may be granted permissions to generate correction reports and prepare deliverable packages. |
| Contributor | A licensed user who has been granted permissions to view and respond to comments made by the Reviewers. |
Contributors are prevented from functioning as Plan Reviewers and may not be granted permissions to the Review page.
The Contributor Role Explained
The Contributor user role is provided for clients who want to invite external customers, or partners, onto a project team for the purpose of collaborating with the plan reviewers.
Contributors do not have access to the Review page and may not conduct reviews. Instead, these individuals can:
- Become members of a project team.
- View comments made by plan reviewers for those projects.
- Receive email alerts when comments have been ‘flagged’ for their input.
- Respond to comments made by the plan reviewers in a secure, user friendly web page.
- View the marked up documents using a PDF viewer, such as Adobe Reader.
- Download the marked up documents if those privileges have been granted
Permission Dependencies for Project records
The Project Workflow Process
For project team members who participate in one or more processes described below, their user roles require the appropriate view, add, edit and optionally delete permissions, to the following entities shown below.
Project Team Membership
- When a plan review assignment is given to a specific user, that individual automatically becomes a project team member.
- Users who add projects automatically become Team members.
- Administrators are automatically granted team membership to all projects.
At minimum, all user roles should have view privileges for Project Management.
Best practices
Project Managers, Group Managers, Reviewers and Contributors should have View priveleges as project Team Members. This ensures that users can see their 'own projects', but not projects they are not team members of.
Permissions Dependencies for Plan Review
Plan Review Workflow Process
For project team members who conduct plan review or who manage plan review staff, their user roles require, at minimum, View permissions to Project Management.
permissions to the entities shown in the diagram below, right:
Default Permissions for the Review Page
Best practices for project team members who conduct plan review via the Review Page are shown in the screen shot below. Modify the settings as desired. Note the typical settings for Group Managers and Reviewers
.
The Contributor user role cannot be granted permission to the Plan Review page. Instead, Contributors may view/download the marked up documents and view/respond to comments for projects they have membership in. Contributors login into a simplified user interface.
Default Permissions for Project Comments
Best practices for team members privileges on the Project Comments Page are shown in the screen shot below. Modify the settings as desired. Note the typical settings for Group Managers and Reviewers and Contributors.
Default Permissions for Comment Responses
Best practices for team members privileges on the Project Comments Responses Page are shown in the screen shot below.
Modify the settings as desired.
Step-by-step guide
Follow these steps to modify permission settings:
- Select Security/Permissions from the Navigation panel
- Drill into the appropriate module
- Toggle the View, Add, Edit and Delete checkboxes and choose the appropriate filter for the desired User Role(s)
- Click Save (required).
Related articles