Page Comparison

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.

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.

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.

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.

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.

A licensed user who has been granted 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.