These permissions apply specifically to the project a user is a member of. They are designed to ensure normal workflow on the project with various members playing their own roles. The default project role applies to any new project the holder of the role is assigned to or an existing one when a project member is assigned the default role. The default project permissions are a preset array of permissions that can be edited to meet the project's specific needs.

By default, Project Manager-role user is not able to edit available roles or even add new users, as this lies specifically with Administrator-role user (or, rather, with one with ‘Manage system settings’ global permission).
The permissions vary widely and are summarized as follows:
Permission |
Description |
Activities
- View all
- Add
- Edit all
- Delete all
- Edit assigned
|
These permissions allow the user to:
- View any activity on the project.
- Add activities of any type to the project.
- Edit any activity on the project.
- Delete any activity on the project.
|
Time entries
- View all
- Add for someone else
- Edit all
- Delete all
- Add own
|
These permissions allow the user to:
- View any time entry on a project.
- Add time entries for activity assignees.
- Edit time entries.
- Delete any time entry.
- Add the user's own time entries.
|
Project
- Edit
- Delete/Archive
|
These permissions allow the user to:
- Edit the project.
- Delete or archive the project.
|
Members and assignees
- View
- Manage members*
- Manage assignees**
|
These permissions allow the user to:
- View project members or activity assignees on the project.
- Manage project members, including assigning from the total pool of users.
- Manage activity assignees.
|
*) This permission refers to managing project members. The permission is the key one for a project manager of the project. It gives a PM the right to add users from the overall list of users. **) This permission refers to activity assignees. It allows the holder of the permission to assign only project members to the project activities. ***) These permissions are independent of the Access to billing information global permission.
|
Ms. Keen is a software developer who has been assigned on a task, GUI for ABC Website, on a project named ‘ABC Website’, is expected, as part of her duties, to be able to view all and edit only tasks, issues or requests assigned to her, as well as view all and edit only issues and requests assigned to her. Regarding time entries, she is entitled to add only her own ones. She is not supposed to modify any details pertaining to the project, or its members as well as those of her co-assignees. The permissions of the type in question in Ms Keen’s role as an EP user on this occasion would be as shown below.
Updating Role for Existing Projects
When you save changes made to a role, they do not take effect for existing projects where the role is used, only for subsequent projects. To apply the updated role to all current projects, if need be, use the 'Apply default permissions in all existing projects' checkbox. As a result, all projects where the role is used will be updated to reflect the changes in default permissions.
Use the option with caution as the update will re-assign the role to the members holding it in whatever project it is used overriding any deviant permissions (marked with *).