Allow setting of approvers and editors for an environment
complete
Johannes Liegl
I'd like the ability to set more granular permissions at the environment level, allowing us to specify who can edit feature flags and who can approve changes directly from the environment settings page, rather than being limited to choosing one or the other.
Log In
d
david.karow
Merged in a post:
Approvals and Restrictions on an environment level
C
Charming Pigeon
Team wants to be able to restrict editing AND require approval, for more security.
d
david.karow
marked this post as
complete
FME Environment by name in RBAC is now live, making the requested capability available now. FME Environment by Type in RBAC is coming soon. Either approach allows you to control edit permissions via RBAC while you can still require permissions per Environment in FME Settings.
d
david.karow
This is now possible with Harness support for FME Environments by Name (and soon by Type) in RBAC. If you control edit permissions via RBAC (see https://developer.harness.io/docs/feature-management-experimentation/permissions/rbac) you can also require approvals in Environment settings (see https://developer.harness.io/docs/feature-management-experimentation/environments#environment-level-fields).
Nicolás Zelaya
marked this post as
long-term