Un-weld setting permissions at the project level, without losing the ability to have project level permissions.

From discussions:
-----------------------------------------
From TQ:
It's cool that labels and permissions can be set at the template or project level, but it seems like these need to be created/managed somewhere else. Two examples: if I have ten projects with the same label, if I want to change the label name, then I have to go into 10 separate projects to change this. Moreover, when setting up projects, admins will need to know/remember label names and type them in correctly. Permissions are more of a nuisance: If I have ten projects where various actions are granted to group Foo, then, during each project set-up, I have to add those actions. If I need to change the actions, then I have to edit those ten projects. I realize that I could set labels and permissions at a template level, but these things don't always have a 1 to 1 relationship. Nor do I want to create a template just to assign permissions (which is what I am doing now). This creates unnecessary and confusing templates.

From me:

Regarding permissions, I see the problem. Would you want to see a default set of permissions associated with each group that is auto populated when you assign the group to a project?. If so, would you expect the permissions for group foo on project x to change if you were to change these defaults?.

From TQ:

If you assign permissions to groups, then people might complain the other way. That is, they may want groups to have a different set of permissions for different projects.

It seems like some sort of construct is needed to cross permissions with groups (e.g. Perms 1/Group 1, Perms 2/Group 1, Perms 1/Group 2, etc), and then assign those to projects/templates.

As it is now, the way that the permissions are set really hinders our ability to set up project templates in highly useful ways.