...

In this article:

...

About User Roles and Permissions

EPR permissions are designed with the following assumptions:

1. Each user is assigned a user role (administrator, project coordinator, project manager, reviewer, group manager or contributor)
2. User role permissions are configured to control how users interact the features and functionality of EPR.

...

About Project Memberships

EPR is also designed with the assumption that:

1. A project 'team', consisting of one or more users, must be created to complete the plan review project.
2. Users who are part of a project team may interact with the project based on their user role and the configured permissions.
3. Users who are not placed into a project team will not be able to view/work on on the project.

...

About Membership Templates

To streamline the process of creating team members for new projects, EPR provides the ability to configure membership 'templates' that include a selected Project Type and a list of users (the Team). 

...

• View existing membership distributions.
• Edit existing membership distributions.
• Add new membership distributions. 
• Inactivate specific membership distributions from being triggered.
• Disabling all memberships distributions from being triggered.

Automatically creating Project Teams

Follow the steps below to configure a project team member 'template' that can be used to automatically assign users to a new project, after a project Type has been selected the new project is initially saved.

...

...

Additional Rules regarding Project Team membership

Regardless of whether membership distribution records have been configured, a project team record will automatically be created:

1. For the user who creates and saves the new project.
2. For the user selected as the Project Manager in the project detail form.
3. For users who are specifically named on a plan review assignment.

...

Related articles

...