In this article:
- Permission Filters and Hierarchy of Privileges
- User Role Definitions
- Permission Dependencies for Projects
- Permission Dependencies for Plan Review
- Default Permissions for the Review Page
- Default Permissions for Project Comments
- Default Permissions for Comment Responses
...
Permission Filters and Hierarchy of Privileges
...
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.
...
User roles cannot be renamed, however, adjusting the permissions for each user roles is supported.
| User Role | Description |
|---|---|
| Administrator | Responsible for user accounts, permissions and configuration. |
| Project Manager | This user typically manages their own Projects. |
| 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 |
| 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 | An external user who has been granted permissions to view and respond to comments made by the Reviewers. |
| Info |
|---|
Contributors are prevented from functioning as Plan Reviewers and may not be granted permissions to the Review page. |
...
- 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.
| Info | ||
|---|---|---|
| ||
Project Managers, Group Managers, Reviewers and Contributors should have View priveleges as project Team Members. This ensures that users can see their 'own projects'. |
...
Permissions Dependencies for Plan Review
...
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 and the appropriate add, edit (and optionally delete) .
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
...
| Info |
|---|
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. |
...
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.
...
- Select Security/Permissions from the Nav 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).
| Info |
|---|
| The Default Permission screen shots above will be helpful if you want to restore the settings to their original (best practices) configuration. |
...