Managing flags in the dashboard

The Flags section in your Vercel dashboard sidebar is the central place to manage feature flags. You can configure targeting rules, weighted splits, progressive rollouts, and coordinate releases for Boolean, String, Number, and JSON flags directly within Vercel.

You can access the flags dashboard by navigating to your project and selecting the Flags section in the sidebar:

Go to Flags tab

The Overview shows all your flags at a glance. You can filter and search to see each flag's status, type, and whether it's currently in use. Flags from Marketplace providers display their provider's icon, while Vercel Flags show a status light. Click on Vercel Flags » Flags on the left to see Vercel Flags only.

To create a flag in the dashboard:

1. From the Flags tab, click the Create Flag button
2. Enter a Slug for your flag (e.g., show-new-feature)
3. Select the Type (Boolean, String, Number, or JSON)

For String, Number, and JSON flags, you can define the variants your flag returns. Each variant has a value used in code and an optional label shown in the dashboard. JSON flags use a code editor for entering structured values like objects and arrays.

When you create a JSON flag, give variants clear labels so they're easier to distinguish later in environment selectors and targeting rules.

During creation, you can configure which variant each environment receives. Boolean flags default to true in Development and false in Preview and Production, so your feature is visible while you develop but hidden after merging. You can refine these rules at any time after creating the flag.

When you create a flag, Vercel automatically configures this environment variable for your project:

• FLAGS_SECRET: Secret key used by the Flags Explorer for overrides

See Feature Flag Configuration for more information on how to configure individual flags.

Select any flag to configure how it behaves across environments and user groups. You can set static values, add targeting rules that evaluate top to bottom, and track the complete history of changes. Rules can target specific segments or entities, with weighted splits for experiments and progressive rollouts for time-based releases.

For more information on how to configure individual flags, see Feature Flag Configuration.

Drafts are flags that Vercel detects in your code but haven't been created in the dashboard yet. This lets you define flags in code first, then promote them when you're ready to configure targeting. When you create a feature flag from a draft the descriptions and options from your code are pre-filled automatically.

For more information on drafts, see Draft Flags.

Segments let you define reusable groups of users, like "Beta Testers" or "Internal Team." Create a segment once with your targeting rules, then apply it to any flag. When you update a segment, all flags using it update automatically.

For more information on segments, see Segments.

Entities define the types and attributes you can target, like User, Team, or Device. By mapping entities to your application data, you can create precise rules like "enable for users on the Enterprise plan" or "show to users in the Engineering department."

For more information on entities, see Entities.

SDK Keys are secrets for manual authentication and cross-project flag evaluation.

To share flags across projects, such as in a microfrontend setup, create a dedicated SDK Key in one project and add it to the other project's environment variables. See How to use flags of another project for details.

For more information on SDK keys, see SDK Keys.

Archive flags when they're no longer needed but you might want to restore them later. Archived flags stop being served and can't be edited while archived, but their configuration is preserved. You can restore a flag with all its previous settings intact, or permanently delete it from the archive.

For more information on archiving flags, see Archive.

• Quickstart guide
• Set up Flags Explorer
• Enable observability