Flags5runtime config
On3of 5
Off2built and not enabled
Scopes3global, tenant, provider
cards.enabled
Card top-up. Built and switched off; the wallet shows it disabled rather than absent.
Global
withdrawals.enabled
Money out, all three panels. Turning this off hides the request button and leaves existing requests in review.
Global
symbols.autolearn
Propose mappings from host-reported specs into an approval queue. Not built; the flag exists so the queue can ship dark.
Global
broadcast.enabled
Close-all and pause-followers. Off would leave a provider no way to flatten followers in a hurry.
Provider
tenant.ownProducts
Tenants publishing their own products from their own masters.
Tenant
What a flag can and cannot do
Two of these are not obvious
- These take effect without a deploy. That is the point of them and it is also the risk: a flag flipped at 17:00 on a Friday has the same reach as a release and none of the review.
- Turning one off does not undo what it did. Switching withdrawals off hides the request button and leaves every request already in review exactly where it is — somebody still has to decide those.
- A feature built and switched off is shown disabled, not removed, where a user has been told to expect it. Cards on the wallet page are the example. The opposite is the Support panel’s credential surface, which is absent precisely so that no flag can turn it on.
- Every toggle is audited with your name and a timestamp. A flag is the cheapest possible change to make and the hardest to remember making.