Reference

Feature flags

Feature access in Quattora is controlled by two systems that work together: plates (the entitlement ladder — free → studio → sales → growth → full_loop → agency, resolved from subscriptions.plan, optionally extended by add-on packs) and the feature_flags table (per-org toggles with role restrictions). Each feature declares a single minPlate — the lowest plate that unlocks it — in packages/config/src/defaults.ts.

How feature access works

Every protected feature passes through four layers:

1. Plate check: Is the org's plate at or above the feature's minPlate (plus any required add-on pack)?
2. Subscription status: Must be active or trialing
3. Feature flag: feature_flags.enabled — is it enabled for this org?
4. Role check: Is the user's role in feature_flags.allowed_roles?

The feature_flags table

One row per feature per org. Seeded from defaultFeatures on org creation.

feature_flags (
  id          uuid PK,
  org_id      uuid FK → organizations,
  feature_key text,          -- e.g. 'crm:contacts'
  enabled     boolean,       -- on/off for this org
  allowed_roles text[],      -- NULL = all roles; array = restrict
  created_at  timestamptz
)

UI: Settings → Admin → Feature Flags (owner/admin only)

Server-side functions

The plate ladder

Plans are strictly nested — every plan includes everything below it. The public self-serve columns are Free, Studio, Team, Firm; Dedicated is sold in a conversation; legacy rungs are hidden and honoured as their successor. Yearly prices, per month, from price book v1:

• Free — $0/mo yearly, $0/mo monthly
• Studio — $29/mo yearly, $35/mo monthly
• Team — $99/mo yearly, $119/mo monthly
• Firm — $249/mo yearly, $299/mo monthly
• Dedicated — $449/mo yearly, $499/mo monthly

Add-on packs extend a plan without changing it: AI Pack ($29/mo, from Free); e-Invoicing / Peppol ($29/mo, from Studio). Keys marked PLANNED below are reserved (wired for gating) but not yet shipped.

Sub-module toggles (Settings → Modules)

feature_flags holds one row per module (crm, invoicing, projects, …) plus, since 2026-09-21, four exact-key rows a workspace can switch inside a module that stays on. Every reader resolves a key the same way (resolveFlagLookupKeys): the exact toggle row if the key is a toggle or one it covers, else the module row, else on. A module that is off wins over a toggle that is on; a toggle with no row inherits its module. The rows are written by the door and by Settings → Modules (applyModuleSelection, audit feature.toggle with a source).

All feature keys

CRM

workspace_data_export is an org flag (not in defaultFeatures) stored in feature_flags; it gates crm:export (CRM → Data Export) together with the crm module. It appears in Workspace admin → Feature flags.

Projects

Platform

AI actions and reserved keys (other modules)

Feature key naming convention

type FeatureKey =
  | `crm:${string}`
  | `projects:${string}`
  | `forms:${string}`
  | `dashboard:${string}`
  | `analytics:${string}`
  | `reports:${string}`
  | `automation:${string}`
  | `invoicing:${string}`
  | `platform:${string}`
  | `ap:${string}`
  | `contracts:${string}`
  | `resource-planning:${string}`

Defined in packages/config/src/types.ts. All keys are used in packages/config/src/defaults.ts (defaultFeatures) and seeded into feature_flags on org creation.