The reason for this is that after a project request has been approved for a portfolio, project permissions are then enforced. Currently all project permission enforcement ensures that the current user is the PM or Alternate PM, as well as ensuring that the project is not in a certain state. For example, a project cannot be closed if it is already closed or it is a private project, even if the current user is the PM or Alternate PM.
However, these project requests that have not yet been finalized as projects have a separate set of permissions enforced. For the Portfolio Planning application, the following permissions are enforced:
- Add Global Searches in Portfolio Planning
- Always Assign Requests to Workflows
- Always Edit Requests
- Staff Requests
- View all project requests belonging to assigned accts/depts
These permissions are enforced while the request is in the process of being approved, and the Project Manager / Alternate Manager are the users who have permission to perform actions on the project. I hope this helps to explain how permissions are being enforced. Please let us know if you would like further clarification or there is anything else we can do to assist you.