Only Account Administrators should be able to assign Project Administrator Access Level

[sfedak]

In general, we need much better permission controls at an account level. Most importantly, we need to prevent members from outside of our organization being accidentally given project administrator rights. Currently, project administrators can just make anyone invited to the project a project administrator as well. We should be able to control, at an account level, who can be given project administrator rights.

It would be great to further this control down to specific permissions to folders in our Docs template as well. For example, we could create a folder that is for internal use only that anyone outside our company cannot be giving access to accidentally by a project administrator. It needs to be controlled at an account level. 

The first option seems to be the easiest lift, and project templates could be tailored enough to accomplish the control you need. However until then, we are very vulnerable to human error. 

[tjones1410]

Related to this is a ability to be able to add project team members without all the privileges of a project admin.

[RobSawall]

Yes.  Permission controls are still out of hand.  We should be allowed the control for Project admins to elevate or change permissions.  We generally set permissions at the company level so that those can be applied to folders.  Roles based permissions could also work if done correctly.  We would love for Project Admins to add users, but not change user or folder permissions.  The option to control permission for Project admins to add companies is a great improvement, but until we can control permissions systematically, we do not leverage project admins.