Feature request:

Split "Create" and "Edit" permissions in feature flags into two separate ACL's that can be assigned to unique roles.

Our use case:

We want certain required parameters to be enforced when creating a flag, we have a script/tooling to do so already. Once created we want users to be able to edit feature flags. Currently nothing is forcing the users to use the scripts, they can continue to create new feature flags from the UI.

They would like little more granularity on the FME Feature Flag resource, imagining an admin can..

Where a manager could have access to:

They want the manager/editor role to be able to separate changing targeting rules from the rest of the flag definition. This will help them better manage their workflow without needing to rely on approving every single change just to make sure end users are following the rules.

Customer would like to be able to restrict on a more granular level. In this case, allow the dev team to be able to instantiate in production, but not make changes to the flags. (Similar to how we allow kills to be bypassed in approval flows.)

This is low priority, as setting up approval flows for this purpose works for now as a workaround.

The level of control over user permissions in FME is too basic for their needs. They'd like to be able to control more specifically who can edit what.