B
Balanced Peacock
Introduce the ability to scope Resource Groups (or another RBAC construct) to a subset of feature flags within a project, for example based on:
* Flag tags
* Flag groups or folders
* Naming conventions or other logical groupings
Administrators should be able to grant users or teams permissions (view, edit, approve, delete, etc.) only for the flags that belong to their scope, while allowing all flags to continue coexisting and being evaluated within the same project.
Example Use Case
A single project may be shared by multiple product teams (e.g., Payments, Mobile, Growth, and Lending). Each team should be able to manage only the feature flags they own, while remaining isolated from other teams' flags. The application continues to consume all flags from the same project, but administrative access is segmented by ownership.
Benefits
* Enables multi-team collaboration within a shared project.
* Reduces the need to create separate projects solely for access control purposes.
* Simplifies governance and RBAC administration.
* Improves security by enforcing least-privilege access.
* Scales more effectively for enterprise customers with large feature flag deployments.
* Aligns administrative boundaries with team ownership while preserving a shared runtime environment.