Skip to content

Feature Flags

Feature flags toggle whole modules on or off. They live under Portal → Settings → Feature Flags. Team admins can lock flags org-wide.

Available flags

FlagModuleDefault
testhubTest Hub catalog and dataset managementon
runnerPlaywright runneron
intelligenceQuality metrics, flaky detection, RCAon
architectureArchitecture auditon
accessibilityAccessibility Auditor (BFSG/WCAG)on
devicelabDevice emulation + multi-browseron
testbuilderURL/description-based test scaffoldingon
brainAI Assistant chaton (needs AI provider)
swarmSwarm QA multi-agent scanson (needs AI provider)
scoutProject Scouton
gitlab / githubCI integrationsoff until configured
youtrack / testrailIssue trackingoff until configured
checkmkMonitoringoff until configured
opsPortalVPS health dashboardenterprise-only
aiProxyCentralised AI proxyenterprise-only

How flags propagate

  • Per user — flip in your own settings, only affects your view.
  • Per team — admins set in Team → Settings → Defaults; pushes to all members.
  • Per project — overrides at the project level for narrow rollouts.

The agent doesn't ship code for disabled flags into runtime payloads, so the local resource cost stays low.

  1. Start with the defaults — they cover 90% of QA workflows.
  2. Disable modules you don't use to keep the sidebar tidy.
  3. Re-enable per-project when you need a feature for a specific repository (e.g. accessibility for a public website only).

Cloud portal · Local Playwright agent.