...
| Info |
|---|
Project Team Membership simply means the user is listed as part of the project team, as seen within the project’s DETAILS > Team sub-tab, and is therefore associated with the project. |
| Table of Contents | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
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.
...
| Info |
|---|
Other permissions can also be restricted to users who are Project Team Members. Refer to Configuring Role-based Permissions for more information about configuring roles and their permissions within EPR. |
...
How Do I Become a Project Member?
...