Versions Compared

Key

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

...

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

...

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?

Since Administrators can require users to be part of a project team in order to view/access the project, it’s important to know the five different methods for becoming a project team member:

...

Method

...

Typical User Role(s)

...

Notes

...

1

...

Any user who creates a project directly in EPR.

...

Project Coordinator, Admin

...

For most integrated clients, the partner system creates the project instead of a staff member.

...

2

...

Any user who is assigned (or reassigned) a plan review task by name (a.k.a. the “Assignee”).

...

Reviewer, Group Manager

...

Any user that can be assigned a plan review task can become a project team member this way.

...

3

...

The first user selected in the Project Manager dropdown from the project’s DETAILS > Info sub-tab.

...

Project Manager

...

This method is specific to the PM role. If no PM is set manually, the first PM user added to a project through another method is listed as the Project Manager. (Additional PMs will not be listed.)

...

4

...

Any user added to a project team from the project’s DETAILS > Team sub-tab.

...

Any

...

User(s) must be selected manually and are only added to that project.

...

5

...

Automated Membership

...

Any

...

Listed user(s) are automatically added to every new project that has matching Purpose and Project Type values, but not to existing projects. (For existing projects, users must be added via another method.)

Info

Once a user is a project member, they will be able to see and access a project at any point until either the project is deleted or the user is no longer a team member.

Automated Membership Distributions

Creating one or more Automated Membership Distributions for any users who are not expected to become project members through other methods can ensure staff always have access to project records. Automated Membership Distributions can be managed by navigating to Settings > Security > Memberships.

...