Master on/off for the entire licensing system. When OFF, _checkTier() and _checkLimit() always return true — every feature is unlocked for every user regardless of their tier. Use this as an emergency fallback if the licensing system has a bug in production. When ON, features are gated based on the user’s resolved tier below.

Overrides the user’s actual tier for testing. Select a tier to force the app into that mode — this is how you test what a Free user vs. Boardroom user sees. “None” means use the real tier from the license key. Persists across page reloads (stored in localStorage).

Max number of swimlanes and total items (milestones + tasks) a Free-tier user can create. When a user tries to add beyond these limits, the app blocks the action and shows an upgrade prompt. Change these to test the limit enforcement with smaller numbers.

Each feature can be set to a tier: Free (available to everyone), Boardroom (requires Boardroom or higher), or Execution (requires Execution tier). This controls what _checkTier('feature_name') returns. When a user on a lower tier tries to use a gated feature, the app shows a lock icon and upgrade prompt instead.

When a user activates a license key, Lemon Squeezy returns a variant name (e.g. “Boardroom Annual”). This table maps those variant names to app tiers. The left field is the variant name from Lemon Squeezy (lowercased, spaces replaced with underscores). The right dropdown is which app tier that variant unlocks.

How to configure: In your Lemon Squeezy dashboard, go to the product → Variants → copy the variant name → enter it here (lowercase with underscores) → select the tier it should unlock. Example: variant “Boardroom Annual” becomes boardroom_annual → maps to Boardroom tier.

Live read-only snapshot of the licensing system’s runtime state. Use this to verify your changes took effect after clicking Apply.

Copies the full current tier configuration as JSON. Paste this into a Claude Code session to set your production defaults in _TIER_CONFIG_DEFAULTS.