This article provides information regarding managing user accounts, project team membership, stamps, and email notifications. Select Security/Users to open the Users page.PrerequisitesAdministrator(s) have the ability to create, update, and otherwise manage their Agency’s e-PlanREVIEW® (EPR) user accounts. This ensures that Admins can regulate how an Agency’s user licenses are apportioned among staff members.
Info |
---|
The following must be completed before additional user accounts can be created:
|
...
|
...
|
A User record requires:
A User Role.
A unique email address and a password.
First and Last name.
User's who will conduct plan review:
Must be associated to one or more Groups.
Should be assigned Stamps.
In this article:
...
Table of Contents | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Understanding Standard and Specialized User Roles
Each e-PlanREVIEW® ( EPR ) user must be assigned a the User Role that most closely matches their expected tasks in EPR.
User Role | License Type | Description |
---|---|---|
Admin (A) | Standard | 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:
|
| ||
Project Coordinator (PC) | Standard | The Project Coordinator is usually reserved for intake staff/permit technicians. |
The |
most common responsibilities for these users are to:
|
|
|
|
|
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. |
| ||
Reviewer (R) | Standard | The Reviewer (or "plan checker", "plans examiner", etc.) has these main responsibilities:
|
|
|
|
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 |
assignments. Reviewers can also create |
corrections reports, 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.
Group Manager
| ||
Group Manager (GM) | Standard | The Group Manager functions as an elevated ‘Reviewer-type’ role.
|
|
|
|
| ||
Project Manager (PM) | Standard | The Project Manager is the highest level of ‘Reviewer-type’ role.
|
|
|
| ||
Contributor (CTR) | Contributor | A Contributor is a non-standard, licensed user who |
is granted access to view and respond |
to plan review staff comments across one or (usually) many projects.
|
|
|
|
|
|
|
|
...
Info |
---|
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:
Click on the plus icon at the bottom right to create a new user account.
Complete the PROFILE tab.
User Role, Password, Email, First Name and Last Name are required.
New accounts must have a unique email addresses that is not already in use by an Active or Inactive account.
Confirm the account is set to Active to ensure the user can log into EPR.
On the GROUPS tab, add which Group(s) the user will belong to.
On the STAMPS tab, select which Stamp(s), if any, that the user should have access to for plan review.
On the NOTIFICATIONS tab, select any desired email notifications for the user (see User Notifications Settings for more information).
Click SAVE.
...
| ||||
Read-Only (RO) | Read-Only | A Read-Only user is a non-standard, licensed user who is granted global view rights to all information within EPR.
| ||
One-Time-Access-User (OTAU) | N/A | A One-Time-Access-User (or “ReviewSession Guest”), is a non-standard, unlicensed role granted to guests invited through the ReviewSession feature so they can view one project’s details, comments, and access pages where those comments exist. The invitation is for a limited time (with an end date set by the invitation sender) and the guest will lose access after that date.
|
A Standard license grants one individual the right to be any one (1) user role within EPR except for Contributor and Read-Only roles, which have their own specialized license types. If you have questions regarding licenses and license types, contact the e-PlanSoft Support Team by creating a Service Desk Ticket.
Info |
---|
Permissions can be changed to either remove or confer additional rights to a user role within certain limits, but it is still recommended for staff to begin with the role closest to their expected behavior. |
Note |
---|
One or more Administrator account is included for technical support purposes (or for performing automated tasks when integrated with a partner system). This account (or accounts) are not included in an Agency’s license count and should not be modified, inactivated, or deleted without prior confirmation from the e-PlanSoft staff. |
...
Creating a New User
Go to Settings > Security > Usersin the Navigation menu to open the Userspage. This page will show Active users - meaning users who can successfully log into EPR - by default.
Info |
---|
To view Inactive users, click on the “Active” toggle so it changes to “Inactive.” |
Note |
---|
Deleted users will not be listed under either “Active” or “Inactive” lists, but they still exist in the database and their email addresses cannot be repurposed for a new account. If necessary, contact e-PlanSoft Support for help with restoring a deleted account. |
Add a User Account
...
Admins can add user accounts as needed from the Users page as follows:
Click on the plus icon at the bottom right to create a new user account.
Complete the PROFILE tab:
Select a License Type based on the intended usage (Standard, Contributor, Read-Only, or Shared).
Password, User Role, Email, First Name and Last Name are required.
New accounts must have a unique email addresses that is not already in use by any Active, Inactive, or deleted user, nor by any Contact records.
Confirm the account is set to “Active”to ensure the user can log into EPR.
Click on the GROUPS tab and select one or more Group(s) which the user will represent when performing plan review.
Click on the STAMPS tab, and select one or more Stamp(s) which the user will be able to place during plan review (if necessary).
Click SAVE to complete creating the account. The form will close.
If the user needs to receive email notifications from EPR, reopen the user profile by clicking (go to arrow).
Click on the NOTIFICATIONS tab, where a list of options now appears.
First, check the box for “Email notifications to…” at the top if this user should receive email notifications from EPR. This may not apply for agencies integrating EPR to another system that can handle user notifications.
Next, select which specific notifications the user should receive (see User Notifications Settings [link] for more information).
Info |
---|
EPR 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 to auto-fill the License Type, User Role, Group(s), Stamp(s) and Notification settings by using the Copy as New User option.
First, select an existing user account.
Click on the ellipsis icon (three dots) on the far right of the account record.
Click on the pop-up for "Copy as New User."
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:
...
) and Notification choices.
To copy an account:
Search for an existing user account to copy.
Click on the (three dots) button on the far right of the record.
Click on the option for Copy as New User.
A new account form pops up with License Type and User Role auto-populated.
Complete the PROFILE tab by inputting a new Password, Email, First Name, Last Name, and any other desired field manually.
Click the GROUPS tab to confirm that desired group(s) are auto-populated.
Click the STAMPS tab to confirm that desired stamp(s) are auto-populated.
Click the NOTIFICATIONS tab to confirm that desired notification(s) are auto-populated.
Click SAVE to complete the new account. The form will close.
...
Info |
---|
Any auto-populated information can be changed as needed while creating a new account. |
Requesting a New Account
To have staff fill out their own basic account information rather than creating it for them, ask any future user(s) to go to the EPR login page and click on Request a new account. This will create the user's account with the basic PROFILE information, but sets their status to “Inactive” and leaves their User Roleblank. The Admin needs to then edit the account(s) to set a user role, make the account “Active”, add group(s), add stamp(s), and select notification options before the user(s) can actually log in.
To view requested account records in the User page:
Toggle the list view from “Active” to “Inactive” at the top of the page.
Search for and select the desired inactive record.
On the Profile PROFILE tab, set the desired 'User Role' and switch the Inactive “Inactive” toggle to Active“Active.”
On the Groups GROUPS tab, select the group(s) the user will belong to.
If necessary, grant access to stamp(s) in the Stamps STAMPS tab.
On the Notifications NOTIFICATIONS tab, select any desired notifications for the user.
The new user will receive an email with login instructions when once their account status has been switched updated from inactive “Inactive” to Active“Active.”
Info |
---|
Administrator's Administrators responsible for managing user accounts should subscribe to the USER - New User Request notification option. |
...
Here is a breakdown of all available notification options and how they are triggered.
Notification Type | Notification Sub-type | Notification Check box | Condition(s) for Notification | Notification Description |
---|---|---|---|---|
PROJECT | Comment | Allow Response | Subscribed AND user is a Contributor. | Notifies user when comment has “Response Enabled” activated. |
User did not create the comment BUT has previously added a response to the comment’s thread. | Notifies user whenever another comment response is added. | |||
User did not create the comment BUT user is currently assigned to the comment. | Notifies user whenever another comment response is added. | |||
User did not create the comment. | Notifies user when they have been assigned to the comment. | |||
User is currently assigned to the comment. | Notifies user when a comment assignment is marked complete/incomplete by someone else. | |||
User created the comment. | Notifies user when another user marks the comment assignment as complete/incomplete. | |||
PROJECT | Document Assignment | Create (Assigned) | Subscribed AND user is named Assignee. | Notifies user whenever they are |
tasked with a review |
assignment by name. | ||||
PROJECT | Document Assignment | Reassigned | Subscribed AND user is named Assignee. | Notifies user whenever they |
become the new assignee for an existing review |
assignment. | ||||
PROJECT | Document Assignment | Status Updated to Active | Subscribed AND is a project team member. | Notifies user whenever an assignment status is changed to any value with the parent status "Active." (These are assignments currently in review.) |
PROJECT | Document Assignment | Status Updated to Approved | Subscribed AND is a project team member. | Notifies user whenever an assignment status is changed to any value with the parent status "Approved." (These are approved assignments.) |
PROJECT | Document Assignment | Status Updated to Canceled | Subscribed AND is a project team member. | Notifies user whenever an assignment status is changed to any value with the parent status "Canceled." (These assignments are not needed.) |
PROJECT | Document Assignment | Status Updated to Not Started | Subscribed AND is a project team member. | 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.) |
PROJECT | Document Assignment | Status Updated to Rejected | Subscribed AND is a project team member. | Notifies user whenever an assignment status is changed to any value with the parent status "Rejected." (These assignments require resubmittal.) |
PROJECT | - | Document Awaiting Intake | Subscribed | Notifies user whenever a document on the Intake tab requires assignments to be created. |
PROJECT | - | Status Changed to Cycle Complete | Subscribed AND is a project team member. | Notifies user whenever a project status is changed to any value with the parent status "Cycle Complete." (This project review cycle is done.) |
PROJECT | - | Status Changed to Finished | Subscribed AND is a project team member. | 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.) |
PROJECT | - | Status Changed to On Hold | Subscribed AND is a project team member. | Notifies user whenever a project status is changed to any value with the parent status "On Hold." (Work on this project has been paused.) |
PROJECT | - | Status Changed to Open | Subscribed AND is a project team member. | Notifies user whenever a project status is changed to any value with the parent status "Open." (This project is undergoing review.) |
PROJECT | - | Status Changed to Withdrawn | Subscribed AND is a project team member. | Notifies user whenever a project status is changed to any value with the parent status "Withdrawn." (Work on this project has been canceled.) |
USER | Auth | New User Request | Admin-role user. | Notifies Admin whenever someone requests a new user account from login page. |
USER | User Account | Create | Admin-role user. | Notifies Admin whenever someone creates a new user account (either from the Users page or API). |
Info |
---|
Some notifications do not require users to subscribe in order to receive them. For example, if a user created a comment, they will be notified when another user replies regardless of whether they are subscribed to a comment event (as long as they have Email notifications to… selected). |
Note |
---|
Note that Project notifications will only trigger for users who are involved in the project as project group team members (these can be users named to a specific review assignment , or just users added to the project and listed in the project's through the DETAILS > Team subsection). |
...
Each user should be subscribed to the events that are relevant to them/their role. The following basic notification subscriptions are recommended:
For Project Coordinators
...
/their role. The following basic notification subscriptions are recommended:
User Role | Description | Example(s) |
---|---|---|
Administrators | Any event notifications, but especially those related to administrative functions such as new user requests and the creation of user accounts any anyone. | |
Project Coordinators | Any notifications related to assignment creation, reassignment, assignment status changes, and/or project status changes. | |
Reviewers, Group Managers, and/or Project Managers |
...
For Administrators
...
Notifications for the assignment or reassignment of a plan review. |
Users subscribed to an event will receive an email notification whenever the event is triggered, as recorded in the event log.
...