Skip to main content
Switchbord uses feature flags to control which product capabilities are active in your workspace. Flags let operators roll out new features gradually, keep unstable surfaces out of production, and trigger emergency stops without redeploying the application. When a flag is off, the product surfaces it controls — campaigns, journeys, inbox features, and more — are hidden or disabled for everyone in your workspace.

​
What feature flags control

Switchbord organizes flags into four categories:
Control which UI sections are visible in the product. For example, a surface flag might show or hide the Campaigns tab or the Journeys builder. If a top-level navigation item disappears, a surface flag is the most likely cause.
Control backend capabilities such as which provider write paths are active or how the worker dispatches queued jobs. Runtime flags affect behavior you may not see directly in the UI but that determines whether sends and automations execute.
Emergency stop flags that disable a specific capability immediately across the workspace. Kill switches are used when a feature needs to be halted without a full deployment.
Control per-workspace cutover state when migrating from a previous messaging platform. Migration flags track which parts of your workspace have completed the transition to the new system.

​
Flag scope

Flag states are workspace-scoped. When a flag is enabled or disabled, that change applies to all members of your workspace — there is no per-user flag override. If you enable a campaign surface flag, every member of your workspace will see the Campaigns section.

​
Viewing flag states

Workspace admins can view the current state of feature flags from the Settings or Runtime pages. The flag list shows:
  • Flag name and category
  • Current state (enabled or disabled)
  • Whether the flag is platform-controlled or operator-adjustable
If a feature you expect to see is missing from the product, check the feature flag state in Settings before raising a support issue. A disabled surface flag is the most common reason a product section is absent.

​
Platform-controlled flags

Some flags are controlled by the platform and cannot be changed from the UI. These flags are managed by your workspace owner through configuration, typically as part of a staged rollout or a migration sequence. The UI marks these flags as read-only so you know they cannot be toggled from the product. If a platform-controlled flag is blocking work you need to do, contact the workspace owner or your Switchbord administrator to adjust the configuration.

​
Default states

Most flags are enabled for development environments by default. Production workspaces have explicit rollout controls, meaning new capabilities may be disabled until you or the platform enables them. Check the flag list in Settings when you move a workspace to production to confirm that the flags you need are active.
After moving to production, review your feature flag states in Settings to ensure no capabilities you rely on were left in their development-default state.