Overrides¶
An override sets an absolute entitlement value for one subscriber and one feature, independent of their plan.
When to use¶
| Use override | Use custom plan |
|---|---|
| Temporary trial of one feature | Long-lived negotiated package |
| Comp / goodwill seat bump | Many features differ from catalog |
| Emergency enable/disable | Sales wants a named package |
Prefer custom plans for real deals. Overrides are surgical.
Properties¶
| Field | Description |
|---|---|
id |
Override id |
subscriber_id |
Subscriber |
feature |
Feature key |
kind |
flag or limit (must match feature) |
allowed |
Flag only: true grant or false revoke |
limit |
Limit only: N or null (unlimited) |
expires_at |
Optional; after this, override is ignored |
created_at / updated_at |
Timestamps |
At most one override per (subscriber, feature) — upsert replaces.
Overrides are absolute, not deltas. To give +5 seats on a plan of 10, set limit: 15, not “+5”.
Resolution¶
If a non-expired override exists for the feature, it wins over the plan:
Flag
allowed: true→ allow even if plan lacks the featureallowed: false→ deny even if plan includes the feature
Limit
limit: 25→ entitled to 25 regardless of planlimit: null→ unlimited regardless of plan