Skip to content

Customize

Some product surfaces in feat are off by default. An admin turns them on when the team is ready to use them. This keeps the dashboard simple for smaller teams and adds capability as you grow.

Open Organization settings then Customize. Each toggle is a boolean.

ToggleWhat it unlocks
Individual targetingAdds the individual targeting section to the flag editor.
SegmentsAdds segments to the project sidebar and the is in segment / is not in segment operators.
Approvals configurationAdds the per-environment approval requirement and the change requests surface.
Progressive rolloutsAdds progressive rollouts to targeting rule menus.

The dashboard hides the corresponding UI. The API rejects requests that touch it with a 404 (the same response you would get for any unknown resource), so a misconfigured client cannot accidentally use a feature you have not enabled.

If a feature was on and you turn it off, the existing data is preserved. Turn the feature back on later and everything is where you left it. The dashboard does not auto-purge: if you decided you do not want individual targets at all, you have to delete them yourself before turning the feature off, or they will reappear when re-enabled.

A typical adoption sequence for a growing team:

  1. Day one: nothing extra. Default flags, targeting rules, percentage rollouts. Most teams ship with this for a long time.
  2. First B2B targeting need: enable segments.
  3. First production discipline pass: enable approvals configuration for the production environment, and per-environment require-comments.
  4. First ramped launch: enable progressive rollouts.

You do not have to follow this order; pick what fits.