BlogRight arrowFeature Flags
Right arrowLess clutter, more control: Manage flag permissions at scale
Backspace icon
Search iconClose icon

Less clutter, more control: Manage flag permissions at scale

Preset Role Scope and Flag Lifecycle Settings can help you issue cleaner, faster releases.

Less clutter, more control: Manage flag permissions at scale featured image

Sign up for our newsletter

Get tips and best practices on feature management, developing great AI apps, running smart experiments, and more.

Subscribe
Subscribe

As your teams scale, so does the complexity of managing access to release controls and maintaining your feature flag ecosystem. This month, we’re introducing two updates to help reduce that overhead: Preset Role Scope and Flag Lifecycle Settings.

These features give platform and engineering teams more consistency and less manual cleanup, so you can work fast without letting complexity pile up.

Preset Role Scope: Cut permission sprawl

Large teams often end up with dozens (or even hundreds!) of custom roles that are almost identical, just applied to different projects. For instance:

  • developer_mobile
  • developer_web
  • developer_infra

With Preset Role Scope, you can define a single reusable role, like developer, and scope it to specific teams or projects. Instead of duplicating roles across the org, you:

  • Define one consistent permission set
  • Apply it to different teams
  • Scope access to just the projects they need

This simplifies onboarding, enforces clear project boundaries, and reduces role clutter. Many teams can now manage dozens of roles with just a handful of scoped templates.

Flag Lifecycle Settings: Configurable stale flag detection

Feature flags are powerful, but unmanaged flag debt slows teams down and clutters codebases.

Previously, LaunchDarkly used a single default definition for when a flag was considered “stale.” But what’s stale for one team (for example, 30 days of inactivity) might be perfectly valid for another.

With configurable Flag Lifecycle Settings, teams can define their own criteria for flag staleness, including:

  • Inactivity thresholds (for example, no changes in 60 days)
  • Flags consistently toggled on/off
  • Usage across environments or segments

When it’s time to archive, LaunchDarkly runs safety checks to confirm that the flag isn’t in use so you can clean up with confidence.

Start scaling feature flags safely and quickly

Both Preset Role Scope and Flag Lifecycle Settings help platform teams scale responsibly without slowing down delivery. These features are designed to make the day-to-day easier for teams managing hundreds of projects and thousands of flags.

Want to learn more? Sign up for a product demo today!

Like what you read?
Get a demo
Previous
Next