Skip to main content

​
Feature Flags

Feature Flags is where team Owners can turn preview capabilities on or off for everyone in the team. It is the mechanism NeuralTrust uses to ship new features incrementally — flags are visible, reversible, and scoped per team so you can opt in to a preview without affecting other tenants. Open it from Team settings → Feature Flags.

​
How flags work

Each flag represents a single capability. For every flag you see:
  • Name and a short description of what turning it on changes.
  • Status — Off, On, or GA (the flag has graduated to default-on and will be removed soon).
  • A toggle to flip it for the team.
Flipping a flag takes effect immediately for new sessions; active sessions pick up the change on next page load. Turning a flag off is always safe — state created while it was on is not destroyed, just hidden.

​
Flag lifecycles

Flags move through a predictable lifecycle. Knowing which stage a flag is in tells you how much to trust it and how long it will stay around.
StageMeaningWhat to expect
PreviewEarly access. The feature is functional but the UX and API may change.Use in non-production first. Feedback welcome.
BetaFeature-complete. API is stable; minor UX polish still landing.Safe for production with awareness that small changes may ship.
GADefault-on for new teams. The flag exists only so legacy teams can turn it off temporarily.Plan to leave it on. The flag will be removed in a future release.
DeprecatedCapability scheduled for removal.Turn off and migrate to the replacement.

​
Who can change flags

Only Owners can toggle feature flags. Admins can view the panel but cannot flip flags. Members do not see the panel at all. Every toggle is logged in Audit Logs with the actor, the flag, and the new value.

​
When to turn a flag on

Good reasons:
  • You want to try a preview of a capability NeuralTrust has announced and are prepared for minor changes.
  • Support asked you to enable a flag to unblock a workflow or as part of a troubleshooting session.
  • Your team is on an older release path and a new default needs to be opted into explicitly.
Less good reasons:
  • Chasing a capability you saw in a demo without testing the interaction with your existing policies first — flip it in a staging team before production.
  • Turning on multiple preview flags at once — isolate one change at a time so regressions are easy to attribute.

​
When to turn a flag off

  • The feature was enabled for a specific investigation and you’re done with it.
  • You enabled a preview and need to roll back for a user-facing reason (UX regression, latency, unexpected interaction with a policy).
  • A flag is listed as Deprecated and you’ve migrated to the replacement.
  • Audit Logs — every flag change is recorded.
  • Release notes — announcements for new flags and flag graduations.
  • Support — reach [email protected] if a flag isn’t behaving as documented or you want access to a preview that isn’t visible on your team yet.