Components are GSA’s optional features, each carrying an on/off flag. Switching one on or off for a client is a setting, not a code change — so a tenancy gets the feature set it needs without a separate build.

This guide covers:

• Turning an optional feature on or off per client through its component flag
• Drawing on features built for one client as capability the next can switch on
• Relying on the platform to log and carry on if one optional feature fails to load
• Recognising that a bespoke per-client data import is the pattern reused, not always the exact build
• Leaving framework and kernel components in place, since neither is client-specific

Use these flags and the same platform serves many clients, each with its own look, rules and features.

💡 Power User Insight: This is a System Administrator or Webmaster task, set per client — distinct from a Site Admin configuring their site’s workflows. A built-in feature-flag system exists but isn’t yet in use.