What Controls Which Apps You Can Turn On
Whether an app's toggle is available, forced, or missing entirely depends on four independent layers stacking on top of each other — not just "on or off":
- Development stage — an app can be published or still in development. In-development apps are hidden from everyone except root organizations, which can opt in "at your own risk."
- Platform availability — separately, a platform operator can withhold an app from the catalog entirely regardless of its stage; a withheld app never reaches your list of toggles at all.
- Applied security model — if your organization has a security model applied (via Branch Types), that model can mark an app as force-enabled (you can't disable it — the switch is locked with a tooltip explaining why) or not available (it's filtered out before you ever see it).
- Billing entitlement — your plan or add-ons determine whether you can actually turn an app on. An app you're not entitled to shows an "Upgrade" or "Add-on Required" chip instead of a working switch.
What this isn't
The help text suggests checking for dependencies between features before disabling one ("some features depend on others being active") — there's no such dependency check implemented today. Nothing stops you from disabling a feature something else in your organization is actively using; there's no warning specific to that scenario.
