The ability to edit the members of a team. Your company may have highly sensitive data and projects that require restriction around who can be assigned to the project. Use this option to define which Project Managers and Process Managers within your organization have the ability to add team members to their projects.

For example, if you are developing products in other countries, or developing products or services that require specific security clearance, it becomes increasingly important to manage the team based on location or specific security credentials. You want to ensure that once a team is set for the product, team members who do not meet the criteria for working on the project are not added.

Users with the Project Manager user role do not require Manage Team rights at the access group level to manage a team. Use the Project Manager can manage team option when assigning a Project Manager to indicate that the user assigned as the Project Manager can add, remove, or replace members on the project's team. If a Project Manager user does have Manage Team rights at the access group level, you can override their Manage Team rights for a single project on project creation, migration, import, and when changing the Project Manager on the team.

Includes the ability to assign gate owners and project managers, add team members, to upload documents without a document owner, and to enter metric values. As a best practice, only one user should have Manage Process rights for a project. Keeping Manage Process rights separate helps to prevent accidentally overwriting each other's changes.

The ability to add a new project using an existing class and model.

The ability to change a project to a different process model.

The ability to delete a closed project from the system.