Feature Sets

A feature set is a named bundle of platform capabilities that you can grant as a unit. They sit between the granular permissions inside security groups and the marketing-friendly subscription packages.

Why They Exist

• Trying to enable 30 individual features on every customer who upgrades is error-prone.
• Subscription packages are the marketing language (“Pro plan”). Feature sets are the technical language. Mapping packages to feature sets gives a clean separation.
• When you launch a new feature, you decide which feature sets get it; existing customers automatically inherit based on their tier.

A Typical Hierarchy

• Starter set: Basic browse, simple forms, single user.
• Pro set: Adds 10 users, custom reports, API.
• Business set: Adds 50 users, audit log, advanced permissions, white-label.
• Enterprise set: Unlimited users, SSO, dedicated support, custom integrations.

Cumulative vs Discrete

• Cumulative: Pro includes everything in Starter plus its own additions. Most SaaS works this way.
• Discrete: Each tier is a distinct bundle, possibly missing features other tiers have. Useful when you sell to specialised audiences (e.g. “Educator plan” has features “Business plan” doesn't).

Worked Examples

• SaaS launch: Three feature sets (Free, Pro, Business) mapped to three subscription packages.
• Add-on architecture: Base sets plus optional add-on sets (e.g. “Analytics add-on”, “API add-on”) that can be enabled separately.
• Educational discount: An “Education” feature set that's a subset of Business — designed for schools at a different price point.

Once you've defined feature sets, you need to link individual features to them. This article shows how to map the matrix of features × tiers cleanly.

The Matrix Editor

Open Architect Panel → Feature Sets → Matrix. Every feature is a row; every feature set a column. Tick a cell to include the feature in that set.

Linking Workflow

1. List every feature your platform has (the platform auto-discovers; you can also add custom).
2. Decide your tier strategy on paper first.
3. Tick the matrix.
4. Save — feature sets immediately reflect the new layout.
5. Test with a sample user in each tier.

Tier Inheritance

To save time, mark a feature set as “Inherits from X”. Anything in X automatically appears in this set — you only have to tick the additions. Cuts the matrix in half for cumulative tier structures.

Worked Examples

• SaaS three-tier: Pro inherits from Starter; Business inherits from Pro. Each tier only ticks its incremental additions.
• Add-on platform: No inheritance — each feature is independently ticked per set. Customers compose their own bundle.
• Legacy migration: Old single-plan customers get a “Legacy” feature set that ticks exactly what they paid for, until their renewal nudges them onto a current tier.
• Free trial: Trial set inherits from Business but flips a “Trial expiry banner” feature on so users see the countdown.

Tip: Run an audit after every tier change. Output the matrix as CSV and review it with sales + product — easier to spot accidental omissions than reading the rows on screen.