@ammario isn't this sort of access control better suited for RBAC than template metadata?

Well this is RBAC too :)

I edited the original post to reflect the points you brought up in Discord about how doing this in the UI/API makes more sense than with config.

Is this different groups than orgs? The current templates are scoped to an organization, and all users on the product are in the first organization.

Is the suggestion to support groups within orgs? At present the RBAC system only supports "organization" grouping of resources.

Is this different groups than orgs? The current templates are scoped to an organization, and all users on the product are in the first organization.

Is the suggestion to support groups within orgs? At present the RBAC system only supports "organization" grouping of resources.

I'm using groups and orgs interchangeably. We should probably revisit the terminology with this fresh start.

Just checking there was not a suggestion to create a second layer of grouping. 1 level of grouping is good 👍.

Terminology wise, happy to change. The code is all saying "organization_id" and already supports this. We just don't expose the creation of multiple orgs atm. Unsure how the cli and ui handle switching orgs atm.

Another prospect has requested this feature: giving specific groups of users access to specific templates.

closed by #4235