Feature Control

Feature Control manages feature flags and remote configuration within a project. Each environment has its own activation state, default allocation and targeting rules. A flag's key, type and variation values are shared across environments.

Create an environment and flagCopy Anchor Link

1. Select a project and open Feature Control under Product.
2. Choose Set up Development and Production to add the missing default environments, or open Environments and choose Create environment. Its identifier is derived from its name; expand the advanced identifier field to override it. Existing environments are preserved.
3. In Feature Flags, select the initial configuration environment and choose Create flag.
4. Enter a name and unique key, select Boolean, String or Number, and provide the Control value and Variant value.

New flags start disabled in the environment where they are created. In other environments they appear as Not configured until you open and save them. Keys and variation values cannot be changed after creation in this release. Use a new flag when you need different values. JSON object values are not yet supported.

Configure evaluationCopy Anchor Link

The default Feature Flags table shows each flag once, with a status for every environment. Select a status to configure that environment. The environment selector in the editor opens the same flag in another environment. Select Enable flag when ready to serve it. A disabled flag causes the evaluator to use the fallback supplied by your application; it does not select the Control variation automatically.

Default allocation applies when no targeting rule matches. Percentages must total 100%, with up to two decimal places. A 0% variation is excluded. For a consistent gradual rollout, applications need a stable user or entity identifier. The optional Bucketing attribute selects a different evaluation-context attribute for allocation.

Targeting rules are evaluated from top to bottom. Every condition in a rule must match. The first matching rule determines the allocation. Use the arrow buttons to change rule order. Numeric comparisons require numeric condition values; contains, starts-with and ends-with require strings. String conditions cannot contain double quotes, backslashes or control characters.

Choose Save changes to save the entire environment configuration atomically. If another user saves first, your draft is preserved. Review the newer version and choose Reset to loaded configuration to discard your draft before retrying. Saving configuration does not deploy an application or provision an evaluation service. Evaluation changes become visible after the configured evaluation service refreshes its configuration.

Connect your applicationCopy Anchor Link

Open SDK Access Tokens, select an environment and copy the SDK Endpoint. Choose Create SDK token and copy the token into your application's GO Feature Flag/OpenFeature provider configuration alongside that endpoint. Tokens begin with rdcf_; they select the environment, while a flag key such as new_checkout identifies a feature in your code.

If the endpoint is not configured, contact support with your project and environment IDs. Application SDKs connect to the evaluation endpoint shown in Console. Service-account tokens are not application SDK credentials.

SDK tokens are shown once. The list displays only their names, prefixes and creation times. Token management requires feature_flags.manage, with up to 10 non-revoked tokens per environment. Use Revoke to request revocation of a token.

Token creation and revocation require platform activation on the evaluation service. Contact support to confirm activation or revocation before relying on the change. Console does not currently show activation status. SDK tokens do not expire automatically.

Feature flags are not a replacement for server-side authorization. Browser and mobile SDK tokens can be extracted from applications. Do not put secrets in flag values or use unverified client attributes to authorize protected operations.

Permissions and limitsCopy Anchor Link

• Viewer and Feature Control Viewer can read flags and values.
• Editor and Feature Control Editor can manage environments, flags and rules.
• Feature Control Admin also has configuration retrieval permission.
• Workspace Owner and Admin can manage Service Accounts and their credentials.
• Up to 20 environments and 200 flags per project.
• Up to 20 targeting rules and 10 conditions per rule.
• Up to 10 unexpired, active tokens per service account.

Deleting a flag removes its configuration from every environment. Deleting an environment removes its configurations, while flags and service-account project grants remain available in other environments. Both actions require confirmation and cannot be undone.

Product navigationCopy Anchor Link

The sidebar keeps Getting started and the resource list available. Opening the product first checks the selected project. A successful, complete empty result opens Getting started; existing resources open the list. Errors and loading states stay in place. Selecting the list explicitly keeps it open even when it is empty.

Lists and resource details use the available workspace width. Getting started links to the existing creation or management flow and documentation; existing permissions still apply.