Overview: Profile-Based Permissions for Projects
What are Profile-Based Permissions?
Profile-based permissions allow you to grant permissions based on your organization hierarchy and ad-hoc groups, as well as individual users. In addition, permissions can be granted at a very granular level; for example, you can grant/restrict access to specific project sections (for example, Details, Notes, Rollups) rather than to the project as a whole. Also, you can grant global read or edit access rights to users (individuals, groups, or org units).
Project Permissions
Project permissions are the set of operations that can be applied to the Project entity, and are listed below:
Note: The Owner of a project is automatically granted full edit Details permissions on the project. You can adjust the profile by adding permissions to the profile, but note that you cannot remove the edit Details permission (even if you uncheck it).
View Permissions |
Edit Permissions |
Create Permissions |
Delete Permissions |
---|---|---|---|
Overview | |||
Details |
Same as View Permissions |
Project Note this is required to be able to change the category of an existing project. |
Projects |
Additional Details |
+ Owner | Note that Edit permissions for tasks, issues, attachments and baselines also grant create permissions on those items. |
Tasks |
Scoring |
+ PMO Locked Fields |
Issues/Risks |
|
Staffing |
+ Scoring Profile |
Notes |
|
Tasks |
(Note that Edit Task includes Create Task) |
Baselines |
|
Fixed Bid |
|
Attachments |
|
Issues/Risks |
(Note that Edit Issue includes Create Issue) |
|
|
Predecessors |
|
|
|
Portfolio Links - must be on team of portfolio with Edit Component Links |
|
|
|
Notes |
|
|
|
Baselines - automatically includes Rollup section | (Note that Edit Baselines includes Create Baselines) | ||
Status Comments |
|
|
|
Attachments |
(Note that Edit Attachments includes Create Attachments) |
|
|
Reports |
|
|
|
Dashboards |
|
|
|
Associations | |||
Rollups |
|
|
|
Team |
|
|
|
Alerts |
|
|
|
Settings |
|
|