The tables below are to help provide some explanations of what is and what is not possible based on permission levels.
Note: Depending on if you are an Online or On-Premise customer (Online = EPM Live hosted & Onsite/On-Premise = client hosted), some areas of the tool might look and/or act differently based on which type of environment you have. For example, when a new user is added to a site, the number and type of email notifications they receive will be dependent upon on their environment. Look for notes throughout this guide that specify how your environment may affect your use of EPM Live.
View the Permission Levels
- Site Collection Admin: The site collection administrator has full rights to the entire site collection, can make any changes to the system and can sync down lists changes.
- Full Control: Have the ability to modify page layout, manage lists and libraries, delete items from a list of library, approve items, create sub sites, and manage security.
- Design: Can view, add, update, delete, approve and customize.
- Contribute: Can view, add, update and delete list items and documents.
- Limited Access (e.g. Contribute w/Delete): Can view specific lists, document libraries, list items, folders, or documents when given permissions.
- Read: Can view, open items but cannot make any modifications.
- Contribute2: Can view, add, update, delete and manage subwebs
View the Security Model Concepts
- View the Security Model concepts.
View the EPM Live Default Resource Groups & Permissions
* Site Collection Administrator (SCA) has the highest level of all permissions.
View the EPM Live Default Build Team and Project Groups & Permissions
- View the EPM Live default Build Team and Project Groups & Permissions.
View the EPM Live Default Associated Items Permissions when Build Team is in Use
Additional Notes: The tables above use an example of team security built on projects and project associated items such as issues and tasks. These same security concepts and rules apply to any other list app where team security is enabled. Other commonly used examples include the following list apps: Programs, Project Portfolios, and Project Departments. In this example the project is the parent item and the project issues and tasks are child items. This concept can be applied to include additional levels/tiers which would be configured by your administrator.
View the EPM Live Default Resource and Cost Planning Permissions
Additional Notes: The table above uses an example of security on the Resource and Cost Planning tools. These same security concepts and rules apply to any other list app where the Resource and Cost Planning features are enabled by your administrator.