Hello KatieLee and thank you for the quick reply!
This is less than ideal, in my opinion. In the Team / Members page, the edit access information lists that the team owner has edit access to all projects and edit access to all files.
At the very least, this is confusing.
How this should work: If a project owner sets the team access for a project to view, this should set access for all team members to view, including team owner. This might be desirable to prevent accidental edits. However, the team owner should be able to self-assign edit access to any project or file within that team, including projects and files the team owner does not own.
- Team owner = root/edit access to all members, settings, projects, and files within that team.
- Admin = similar to team owner except cannot remove team owner.
- Team member with team edit privileges = suggested rename to Editor = can create, access, remove, edit, and view all projects and files except where explicit access is revoked at the project level by the project owner or file level by file owner. Cannot access team members or settings.
- Team member with team view privileges = suggest rename to Reviewer = can view all projects and files except where explicit access is revoked at the project level by the project owner or file level by file owner. Cannot create projects. Can only edit projects or files where permissions explicitly granted. Can create files in projects with edit access.
- Team member = can only view or edit projects and files with view or edit access explicitly set. Can only create files if project edit access is granted.
This is just a sketch. I can see this gets complicated and you guys know much better than me of course. To properly map this out would take much more detail. Not that you even asked ha ha.
When this problem occurs: when a team member with edit access creates a new project, if they set team access to view, the team owner cannot edit, remove, or change sharing access to that project or any files contained within.