Skip to content
OclavexOclavex Docs

Add-ons

An add-on is granted on top of an entitlement that already has a plan; an add-on is never the base grant. It packages two things together:

  • a suite — which suite’s catalog it may add features from;
  • feature choices — which catalog features are included, with any value overrides.

An add-on moves through Draft → Published → Archived; only a published add-on can be granted.

Entitlement suite: Design Suite · plan: Pro Seats 5 Export ✓ the plan's features — the base Add-on published suite: Design Suite Seats +10 · on Pro Priority support included feature choices same suite base add-on grant starts · expires · revocable What the customer has right now Seats 15 5 + 10 Export ✓ from the plan, untouched Priority support ✓ added by the add-on Resolved when you ask — the entitlement's base is never edited.

Layer onto an existing plan

Section titled “Layer onto an existing plan”

Grant an add-on to an entitlement and its feature choices layer on top of whatever the entitlement’s own plan already grants — no re-picking the base plan per customer. When you resolve “what does this customer have right now”, active add-on grants overlay the entitlement’s base.

Keep selling an add-on while your plans move on

Section titled “Keep selling an add-on while your plans move on”

An add-on overlays the suite itself, not one version of its plans. A published plan set is never edited in place — an edit lands on a draft revision, and publishing that revision retires the previous one — and the add-on stays grantable across all of them: an entitlement on the older revision and one on the newer revision can both hold the same add-on grant.

An add-on can also aim a feature choice at named plans only — “these extra seats apply on Pro”. Plans are matched by name, so Pro in the new revision is the same Pro.

How it relates

Section titled “How it relates”