Versions Compared

Key

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

Project visibility and access within e-PlanREVIEW® (EPR) may be regulated by Administrators through the user role permission settings. While Agencies can keep all projects visible/accessible to most users, those which prefer to regulate projects more tightly can make Project Team Membership a requirement in order to work on a project. Agencies who use this additional requirement should be familiar with the ways that users can automatically become a Project Member and also as well as how to set up one or more Automated Membership Distributions to help fill any gaps where none of the other methods apply.

Info

Prerequisites for creating automated membership distributions:

  1. Project Types must be configured. See Managing List Types and List Items.

  2. User accounts must be created. See Managing User Accounts.

  3. Permissions must be set. See Permission Dependencies for Project records.

Table of Contents
minLevel1
maxLevel6
include
outlinefalse
indent
exclude.*Related articles.*
typelist
class
printablefalse

User Roles, Permissions, and Project Membership

Permission settings allow an Admin to globally modify behavior for each kind of user role within EPR. By default, a standard EPR implementation will have project “View” permissions set to GLBL - Global Access for most roles. User roles with this setting can view all projects once logged into EPR. (“Add”, “Edit”, and “Delete” rights then regulate what else each user role can do within a project, if anything. Project Coordinators can usually do more at the project level than a Reviewer, for example.)

For many agencies, the defaults are perfectly fine. Others may prefer to restrict which projects are visible to a user, either as a result of preferred business rules or simply to help keep users focused and on task. Typically this alternative involves setting the additional requirement of Project Team Membership, which occurs when changing the Project Management “View” filter to PROJ - Project Member for one or more user roles.

Anyone logging in with one of those user roles, then, will only be able to view projects where they are listed as a project team member within the project DETAILS > Team sub-tab, as shown below.

...

...

Automated Membership Distributions

...

  1. Click on Add ( (blue star) ) in the lower right corner to create a new membership distribution.

  2. In the “Add/Edit Memberships” pop-up, make sure the Active toggle at the top is pointed to the right.

  3. Click on the Purpose drop-down. The distribution will only apply to the selected Purpose.

  4. Click on the Project Type drop-down. The distribution will only apply to the selected Project Type.

  5. From the table, select one or more users who should be automatically added as project members whenever a new project is created with the matching Purpose and Project Type. ( If you have a large user list, you may want to alter can:

    1. Type into any of the headers at the top of the table to search for either a specific user, user role (using the abbreviation), or filter for members of a specific group

    2. Alter the number of rows displayed

    by default, otherwise you may need to click Next and Previous to view the full list.
    1. when you scroll (found at the bottom of the table)

    2. Navigate between records using the Next and Previous buttons (found at the bottom of the table)

  6. Click CONFIRM to save the automated distribution.

...