Skip to main content
Back to Blog
extensions features configuration workspaces

Feature Extensions: Enable What You Need

Swifty Team Feb 7, 2026 3 min read

Not every business needs every feature. A consulting firm doesn't need inventory management. A retail operation doesn't need client project timelines. A logistics company doesn't need invoicing workflows.

When a platform ships all features enabled, every workspace carries the weight of capabilities that most of its users will never touch. Navigation gets crowded. Configuration gets complex. Users encounter options that don't apply to their work.

The feature extension system solves this.

On/Off Per Workspace

Each capability in the platform is packaged as an extension. Extensions are enabled or disabled at the workspace level. When an extension is disabled, its features don't appear — no menus, no configuration options, no data types, no screens.

Enabling an extension makes its features available immediately. No restart, no deployment, no waiting. The platform assembles the experience based on what's enabled, adding the extension's components to navigation, definitions, and available configurations.

Clean by Default

A new workspace starts clean. You enable the capabilities that apply to your business. As your needs evolve, you enable more extensions. If something isn't working for your team, you can disable it without affecting anything else.

This creates a clear separation between the platform's full capability set and the experience your specific workspace offers. The platform can be comprehensive — covering many domains and use cases — while each workspace remains focused.

Extensions in Practice

An e-commerce extension adds order synchronization, product catalog management, and shipping integrations. A financial documents extension adds invoicing, payment tracking, and tax computation. A scheduling extension adds calendar views and appointment booking.

Each of these has real complexity. When enabled, that complexity is available. When disabled, it doesn't exist as far as the workspace experience is concerned.

No Interference Between Extensions

Extensions are designed not to interfere with each other. Enabling two extensions that both add to the navigation doesn't create conflicts — the platform merges their contributions according to defined rules.

An extension that's disabled doesn't affect the behavior of extensions that are enabled. Each is isolated, activated only when explicitly turned on.

Your App, Your Scope

The extension system is ultimately about focus. A focused app is easier to learn, easier to use, and easier to manage. Your team sees only what's relevant to their work. Configuration options apply only to features they're actually using.

Turn on what you need. Leave off what you don't. Adjust as your business changes.

Related posts

Composed Data Sources

Chain and relate data sources for rich dashboards — compose complex data views from simpler sources without writing code.

Computed Expressions

Transform data with template expressions and built-in functions — format, combine, and derive values from your data without code.

Cross-Source Data Joins

Combine data from multiple sources in one view — join records from your database with data from external services using a shared key.