ST-2026-238 · SDKs & toolchains
Atlassian Forge Feature Flags Client SDK ends anonymous-user support on 1 December
Starting 1 December 2026, Atlassian's Forge Feature Flags Client SDK will stop evaluating feature flags without an authenticated accountId and will fall back to default values for anonymous users.
Previous state
Forge apps could initialize the Feature Flags Client SDK without a logged-in user or accountId and receive evaluated flag values for anonymous-access experiences.
Current state
From 1 December 2026, FeatureFlags.initialize() functions only for authenticated users with a valid Atlassian account; anonymous initialization returns no evaluated values and uses the configured defaults.
Affected users
Who needs to care
Forge apps that use FeatureFlags from @forge/bridge and serve unauthenticated users through modules with unlicensedAccess or another anonymous-access path.
Required response
What to do
Detect the absence of accountId and use a deliberate default for anonymous users, or move anonymous flag logic to the server-side SDK using installContext before 1 December 2026.
Evidence boundary
What the source does not prove
Atlassian proves removal of anonymous-user evaluation in the Forge Client SDK. Authenticated users remain supported, the server-side SDK has a separate installContext option, and Feature Flags as a whole are not retired.
Lifecycle history
Dated event sequence
- Deprecation notice issued
Atlassian announced a 90-day deprecation period for anonymous-user evaluation.
- Breaking change scheduled
Anonymous Client SDK initialization stops returning evaluated feature-flag values.
Evidence ledger
First-party sources
- 01Atlassian — Removing support for anonymous users in Forge Feature Flags Client SDK
Official Atlassian developer changelog · 2026-09-02
Open official source ↗