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
- List every feature your platform has (the platform auto-discovers; you can also add custom).
- Decide your tier strategy on paper first.
- Tick the matrix.
- Save — feature sets immediately reflect the new layout.
- 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.