Control Permissions Per Template, Not Template Folder
I think having permissions based on template folders is flawed... We want to be able to organize our templates in a way that is useful to our users, which is not always the same way we want to provide permissions for editing templates, seeing other's forms, etc.
I want to be able to organize my templates in whatever folders I want. I additionally want to be able to give people access to individual templates regardless of what folder they are organized in. If I want someone to be able to edit a single template within a folder, but none of the other templates within that folder, I should be able to do that.
Right now, I have to choose between a folder structure that is easy for my end users to navigate through or a folder structure that meets my access control needs. These two things should not be dependent on each other.

Our team is exploring this idea, please share your comments and feedback so we can continue our discovery.