Organization features
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.
The toggles
Section titled “The toggles”Open Organization settings then Features. Each toggle is a boolean.
| Toggle | What it unlocks |
|---|---|
| Anonymous contexts | Targeting rules can match contexts marked anonymous: true. SDK supports anonymous evaluation. |
| Flag maintainer | Adds a maintainer field to every flag. Used for search and ownership attribution. |
| Individual targeting | Adds the individual targeting section to the flag editor. |
| Segments | Adds segments to the project sidebar and the is in segment / is not in segment operators. |
| Scheduled changes | Adds the scheduled changes action to the flag editor. |
| Approvals configuration | Adds the per-environment approval requirement and the change requests surface. |
| Multi-step workflows | Adds workflows to the flag editor. |
| Progressive rollouts | Adds progressive rollouts to targeting rule menus. |
What happens when a feature is off
Section titled “What happens when a feature is off”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.
Order of enablement
Section titled “Order of enablement”A typical adoption sequence for a growing team:
- Day one: nothing extra. Default flags, targeting rules, percentage rollouts. Most teams ship with this for a long time.
- First custom dimensions: enable flag maintainer so ownership is visible in audit and search.
- First B2B targeting need: enable segments.
- First production discipline pass: enable approvals configuration for the production environment, and per-environment require-comments.
- First scheduled launch: enable scheduled changes.
- First ramped launch: enable progressive rollouts.
- First multi-step release: enable workflows.
You do not have to follow this order; pick what fits.
Related
Section titled “Related”- Core concepts for the short version of which feature lives where.
- Members and roles for who can flip these toggles.