Managing Feature Flags

This guide covers how to manage your feature flags using the IntelliToggle Dashboard. You’ll learn how to create, organize, and maintain flags across multiple environments, along with best practices for lifecycle management.

Accessing the Dashboard

To manage flags, log in to the IntelliToggle Dashboard.

You’ll need an account with appropriate permissions (e.g., developer or admin role).

Creating a New Feature Flag

To create a new flag:

  1. Navigate to the Feature Flags section.

  2. Click "New Flag".

  3. Fill in the required details:

    Field Description

    Name

    Unique identifier used in SDK code (e.g. enable_dark_mode)

    Description

    (Optional) A human-readable note about the flag’s purpose

    Type

    Choose from: boolean, string, number, json

    Default Value

    The fallback value when no targeting rules match

    Environments

    Select which environments the flag should apply to

  4. Click Save.

The flag will now be available via the SDK using the name you provided.

Editing and Updating Flags

From the dashboard, you can click on any existing flag to:

  • Update its default or environment-specific values

  • Edit its description

  • Change targeting rules

  • View usage analytics

Changes take effect immediately in the environments selected.

Environment-Specific Values

Each flag can have different values across environments (e.g., dev, staging, prod). Use the tabbed environment view to configure:

  • Default Value – fallback when no conditions match

  • Override Rules – e.g., enable for 10% of users in staging

Targeting Rules

You can define rules to segment users based on context passed by the SDK.

Example targeting options:

  • user ID

  • email or domain

  • region or country

  • platform or device

  • custom attributes

To add targeting:

  1. Open a flag

  2. Navigate to the Targeting Rules section

  3. Add one or more conditions (e.g., user_id is one of test-user-1, test-user-2)

  4. Optionally define a percentage rollout or fallback behavior

See how to pass user context to the SDK.

Organizing Flags

Flags can be organized with:

  • Tags (e.g., onboarding, experiment, internal)

  • Projects or Namespaces

  • Search & Filter: Quickly find flags by name, tag, or environment

Organizing flags helps avoid clutter and simplifies audits or cleanup.

Toggling Flags

Use the status toggle to enable or disable a flag without deleting it:

  • Green = Enabled (value is active in targeting rules)

  • Gray = Disabled (SDK will return the fallback)

This toggle is especially useful for kill switches and staged rollouts.

Deleting or Archiving Flags

You can remove unused flags, but consider archiving instead for audit history.

  • Archive: Keeps the flag in the system but prevents SDK evaluation

  • Delete: Permanently removes the flag and all metadata

Flags in use by client code should never be deleted until references are removed.

Best Practices

  • Use descriptive flag names (e.g., enable_beta_nav)

  • Set clear default values across environments

  • Regularly review and clean up old or unused flags

  • Document the owner and purpose of each flag

  • Group flags by tag, feature, or team when possible

Read more about flag lifecycle management.

What’s Next?

Now that you’ve learned how to manage flags, continue with: