Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In this article:

Table of Contents

...

Users with an 'Administrator' user role have 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 may be necessary for view, edit, update and delete privileges of projects, documents and versions, plan review assignments and reviewer comments.

...

User Role Definitions

User roles cannot be renamed, however, adjusting determine the permissions for each user roles is supportedan account within EPR. Since permissions are configured at the user role level, all users with the same role will have the same permissions.

Each User Role is pre-configured with default permissions to match the role's typical expected tasks within EPR, but many role permissions can be adjusted by the Admin. The Admin cannot rename the User Role labels, however.


User RoleDescription
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
prepare deliverable packages.

Project ManagerThis user typically manages their own Projects.Group ManagerThis user manages plan reviewers in his Group(s) and may be granted permissions
to edit/delete markups for users in his Group(s).ReviewerThis individual conducts plan reviews and may be granted permissions to generate correction
reports and prepare deliverable packages

The Admin role is tasked with assisting in the initial configuration of the EPR portal. This user can update portal configurations that affect permissions, assignment workflow, email, and even portal branding as needed. The Admin can also manager user accounts within EPR.

Some of the most significant Admin abilities include managing:

  • User accounts
  • Assignment distribution workflows
  • The standard comment library
  • Corrections Report Letter templates
  • Stamps and user stamp access
  • Email notification templates
  • Drop-down list values

The Admin role can also perform the functions of every other user role in EPR, including project creation, assignment intake, plan review, and packaging deliverable back to applicants.

Project Coordinator

The Project Coordinator is usually reserved for intake staff/permit technicians.

The main responsibilities for these users are to:

  • Create plan review tasks (“assignments”) for reviewers
  • Update assignment tasks or reassign, as needed.
  • Prepare corrections report letters (typically)
  • Prepare deliverable packages of marked-up or approved plans to send back to applicants at the end of a review cycle.

When all review assignments have been given an approved, rejected, or canceled status, Project Coordinators will be notified so they can prepare a Corrections Report letter with all reviewer feedback and then package files to return to the applicant, either through email or, more commonly, through check-in to an integrated portal.

This user role typically cannot perform plan review.

Reviewer

The Reviewer (or "plan checker", "plans examiner", etc.) has these main responsibilities:

  • Review and markup plans submitted by an applicant
  • Provide feedback through comments and/or stamp approved plans as appropriate.
  • Evaluate the submittal by setting an assignment Status (Approved, Resubmittal Required, etc.)

Reviewers belong to one or more Groups (think of these as Departments or Sub-departments) and are responsible for completing plan review tasks (“assignments”) made for their Group. In some cases, especially for larger agencies, assignments are made for a specific named Reviewer within a Group. Although other users are still able to access the assignment, the named Reviewer is expected to complete the review assignment task.

At the end of a review cycle, the reviewer must provide either an approval, rejection, or other status for the assigned plans and, if appropriate, may stamp plans as well. Reviewers can also create Corrections Report letters, if desired. The Reviewer role is not configured to perform intake of plans or prepare deliverable packages to send back to an applicant – for this functionality, see Project Coordinator.

The Reviewer role is not configured to perform intake of plans or prepare deliverable packages to send back to an applicant – for this functionality, see Project Coordinator.

Group Manager

The Group Manager functions as an elevated ‘Reviewer-type’ role.

  • The difference is the GM has the added ability to edit and delete markups created by other reviewers within his or her Group (by default, a reviewer can only edit his or her own markup activity).

A Group Manager cannot edit or delete markups for another Group unless they also belong to the other Group.

Project Manager

The Project Manager is the highest level of ‘Reviewer-type’ role.

  • The difference is the PM has the added ability to edit and delete markups created by other reviewers within the project he or she is managing.

A Project Manager cannot edit or delete markups for another Project unless they also manage that Project.

Contributor

A licensed user who has been granted

permissions

access to view and respond to comments made by the Reviewers in an existing project.

  • The contributor can view projects for which they are a "team member" (part of the Project Team).
  • They can view those project comments and add responses to any that have the 'response enabled' option set by the reviewer.

They cannot respond if response is not enabled, nor can they create new comments or markup plans. This user role cannot perform plan review.


Info

Contributors are prevented from functioning as Plan Reviewers and cannot be granted permissions to so they cannot perform markup, but they can access the Review page as of a recent update.

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. This provides the contributor with project access, as shown below (steps 1-3):

Image Added

  • View comments made by plan reviewers for those projects

...

  • (4), apply filters (5) and check whether any are flagged by reviewers as priority comments (6).

Image Added

  • Respond to comments made by the plan reviewers in a secure, user friendly web page (7-11).

Image Added    

Image Added    

Image Added   

 Image Added

  • View

...

  • the comments on the plans pages through the EPR Review page.
  • Download the

...

  • documents if those privileges have been granted.

While comments are visible to contributors once they become a project team member, the ability to respond to a comment is controlled by the reviewer who creates the comment ("Response Enabled" feature). At any point during the plan review, if a Contributor is granted access to a project then they will be able to view and respond to comments concurrently with the remainder of the review cycle. Comments added by contributors are placed below the most recent version of the reviewer's comment, and if reviewers update their comment then this updated version will display below the contributor's comment to maintain the chronology of the conversation as clear as possible. Contributor project access can be revoked, if desired, by an agency Admin at any time by removing the user from the project team.


NEW! Contributors can now view a comment directly on the EPR Review page to see it in context. From the Project Comments page, the Contributor hovers over the comment text to display the → (right-facing arrow) icon, as show below. Click on this button (→) to navigate to the Review page.

Image Added

While on the Review page, Contributors can see the comments on the document page and access attachments to comments (if any), but cannot markup or otherwise modify the plans.

Image Added


...


Best Practices for Configuring Permissions for Project Access

...

When the permission filters are set Project Team memberMember, users who open the Projects page will only see records for projects in which they are a project team member as opposed to all projects that may exist globally. In the same manner, users who open the Assignments page will only see open assignment records for projects in which they are a team member, as opposed to open assignments that may exist globally. 

...