Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 36 Next »

This article provides information regarding managing user accounts, project team membership, stamps, and email notifications. Select Security/Users to open the Users page.

Prerequisites:

  1. Configure User Role Permissions.
  2. Configure Groups for Permitting and Design Review Lists.
  3. Upload Stamps.

A User record requires:

  1. A User Role.
  2. A unique email address and a password.
  3. First and Last name.
  4. User's who will conduct plan review:
    1. Must be associated to one or more Groups.
    2. Should be assigned Stamps.


In this article:



Understanding User Roles

Each e-PlanREVIEW® (EPR) user must be assigned a User Role that most closely matches their expected tasks in EPR.


User RoleDescription
Admin

The Admin role is mainly tasked with assisting in the initial configuration of the EPR portal and with updating portal configurations as needed.

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 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.


Full licenses grant the right for a user to be any one of the non-contributor roles, which give them access to the markup tool, access to project records, and/or internal functions such as document intake, creating deliverable documents, or even portal configuration (based on the specific role’s permissions).



An Administrator account is included for technical support purposes. This user account is read only.



Creating a New User

Go to Settings > Security > Users in the Navigation menu to open the Users list. This page will show 'Active' users, meaning users who can successfully log into EPR, by default. (To view inactive users, click on the Active toggle so it changes to Inactive.)

Add a User Account

Admins can add user accounts as needed from the Users list page as follows:

  1. Click on the plus (plus) icon at the bottom right to create a new user account.
  2. Complete the PROFILE tab.
    1. User Role, Password, Email, First Name and Last Name are required.
    2. New accounts must have a unique email addresses that is not already in use by an Active or Inactive account.
    3. Confirm the account is set to Active to ensure the user can log into EPR. 
  3. On the GROUPS tab, add which Group(s) the user will belong to.
  4. On the STAMPS tab, select which Stamp(s), if any, that the user should have access to for plan review.
  5. On the NOTIFICATIONS tab, select any desired email notifications for the user (see User Notifications Settings for more information).
  6. Click SAVE.

e-PlanREVIEW monitors the total count of active user accounts to compare this to the purchased user license count. Only active accounts are counted toward the license total. Inactivating a user account will free up a license for other personnel.

Copy an Existing Account

Admins can save time when creating a new account by copying an existing profile's User Role, Group(s), Stamp(s) and Notification settings by using the Copy as New User option.

  1. First, select an existing user account.
  2. Click on the ellipsis icon (three dots) on the far right of the account record.
  3. Click on the pop-up for "Copy as New User."
  4. Complete the new account by providing any missing information, such as the new user's unique email address, and save when completed. (You can also modify existing configurations before saving.)


Requesting a New Account

If an Admin wants staff to fill out their own information, they can ask a future user to "Request a new Account" from the EPR Login page. This creates the user's profile with a temporary password, but sets their status to Inactive and leaves their user role blank. The Admin would then need to define a user role and switch the account to Active to give the user the ability to log in.

To view 'requested account' records in the User list:

  1. Toggle Active to Inactive at the top of the page.
  2. Search for and select the desired inactive record.
  3. On the Profile tab, set the desired 'User Role' and switch the Inactive toggle to Active.
  4. On the Groups tab, select the group(s) the user will belong to.
  5. If necessary, grant access to stamp(s) in the Stamps tab.
  6. On the Notifications tab, select any desired notifications for the user.
  7. The new user will receive an email with login instructions when their account status has been switched from inactive to Active.


Best Practices

Administrator's responsible for managing user accounts should subscribe to the USER - New User Request notification option.



User Notification Settings

Admins can choose which events will trigger an email notification for a user from the user account NOTIFICATIONS tab. Users can only be subscribed to the events that appear in the Notifications tab, and not all events are available for all user roles. (For example, only Admins can subscribe to receive 'New User Request' notifications.)

How to Set Notifications

To configure user email notifications:

  1. Search for a user account.
  2. Click on the right-facing arrow to 'Edit' the account.
  3. Click on the Notifications tab.
  4. Set the 'Email notifications to...' checkbox for the user, as needed.
    1. Place a check mark next to the notifications that should trigger emails to this user.
  5. Click the SAVE button.


Notification Options

Here is a breakdown of all available notification options and how they are triggered.


PROJECT Notifications

  • Comment
    • Allow Response - For CONTRIBUTOR ONLY. Notifies Contributor whenever a comment has 'Response Enabled' set. (This is not the same as notifying a user whenever a comment response has been written.)


  • Document Assignment
    • These notifications will ONLY trigger for the named assignee:
      • Create (Assigned) - Notifies user whenever they are assigned a review task by name.
      • Reassigned - Notifies user whenever they are re-assigned an already existing review task.
    • These notifications will trigger for any user who subscribes AND is a project team member:
      • Status Updated to Active - Notifies user whenever an assignment status is changed to any value with the parent status "Active." (These are assignments currently in review.)
      • Status Updated to Approved - Notifies user whenever an assignment status is changed to any value with the parent status "Approved." (These are approved assignments.)
      • Status Updated to Canceled - Notifies user whenever an assignment status is changed to any value with the parent status "Canceled." (These assignments are not needed.)
      • Status Updated to Not Started - Notifies user whenever an assignment status is changed to any value with the parent status "Not Started." (Review for these assignments has not yet started.)
      • Status Updated to Rejected - Notifies user whenever an assignment status is changed to any value with the parent status "Rejected." (These assignments require resubmittal.)


  • Project
    • Document Awaiting Intake - Notifies user whenever a document on the Intake tab requires assignments to be created.
    • These notifications will trigger for any user who subscribes AND is a project team member:
      • Status Changed to Cycle Complete - Notifies user whenever a project status is changed to any value with the parent status "Cycle Complete." (This project review cycle is done.)
      • Status Changed to Finished - Notifies user whenever a project status is changed to any value with the parent status "Pass" or "Fail." (This project has been approved or requires resubmittal.)
      • Status Changed to On Hold - Notifies user whenever a project status is changed to any value with the parent status "On Hold." (Work on this project has been paused.)
      • Status Changed to Open - Notifies user whenever a project status is changed to any value with the parent status "Open." (This project is undergoing review.)
      • Status Changed to Withdrawn - Notifies user whenever a project status is changed to any value with the parent status "Withdrawn." (Work on this project has been canceled.)


Note that Project notifications will only trigger for users who are involved in the project as project group members (these can be users named to a specific review assignment, or just users added to the project and listed in the project's DETAILS > Team tab).


USER Notifications (for Admin only)

  • Auth
    • New User Request - Notifies Admin whenever someone requests a new user account from login page.
  • User Account
    • Create - Notifies Admin whenever someone creates a new user account (either from the Users page or API).



Recommended Notifications

Each user should be subscribed to the events that are relevant to them/their role. The following notifications are recommended:


  • For Project Coordinators


  • For Reviewers, Group Managers, and/or Project Managers


  • For Administrators

 


Users subscribed to an event will receive an email notification whenever the event is triggered, as recorded in the event log.




Inactivate or Delete User Accounts

Inactive Account status

  1. Users with an Inactive status do not have login privileges.
  2. Inactive user accounts can be reactivated at any time.
  3. Inactivating a user account frees up a user license for another individual.

Notifying users of login privileges

An email will automatically be sent to a user when their active status is changed from Inactive to Active.

Deleting a User account

  1. From the Users List, open the user form.
  2. Select the ellipsis icon on the upper right corner of the user form and choose Delete.
  3. Click Confirm to delete the user account.
  4. A deleted user account can be restored, if that becomes necessary. Submit a help desk ticket to the e-PlanSoft team for assistance.


Because email addresses must be unique, you may not create a new user account that has the same email address as an active, inactive or deleted user. 



Removing Users from Groups

In situations where a user has been personally assigned reviews to complete for a Group, and is then removed from that Group, the following will occur:

  1. The user retains rights to edit their existing comments and sketches, measurements and stamps on those assignments.
  2. While the user remains the 'named user' for the assignment, they retain the right to change the assignment status.
  3. The user cannot create new comments, sketches, measurements and stamps for that Group, to which they no longer belong.


















  • No labels