Feature flags and rollout
Which capabilities are switched on, for whom, and how a rollout is advanced or rolled back.
Note: This screen has no data behind it in this build
The address is specified and the console is ready for it. What is missing is the server side: the reads below are declared by the contract and are not registered in this deployment, so they answer “not implemented” rather than returning anything. Nothing on this page is a placeholder for data — there is no data to place.
What this screen is for
Each flag with its current value, the audience it applies to, and a previewed change to advance or roll back a rollout — with the same preview and approval a privileged change gets elsewhere, because a flag change is a change to what customers can do.
What has to exist first
- Reads
- staffFlagsList
- Actions
- staffFlagPreview
- staffFlagPublish
- staffFlagRollback
Each of those is an operation id in the frozen contract. Registering one is a server change, not a permission you can be granted — no group and no scope makes this screen return data today.