Entitlements

Negotiated Feature Access Without a Pile of Account-Specific Code

By the Orvlin team · · 2 min read

Contract specific entitlements: what to decide

Sales agrees to include advanced exports for one annual customer. An engineer adds an if statement. After several deals, the product has a hidden second catalog that only a few people understand. Commercial exceptions need a visible home.

Start with the standard plan, then apply the approved override with its scope and expiry. Record who authorized it and whether renewal retains it. Keep the resulting effective access explainable to support and the customer.

How this works in practice

An account gets 50 seats instead of the standard 20 until its contract ends. A dated capacity override is easier to audit than editing the shared plan, which would accidentally grant 50 seats to every customer.

What can go wrong

An override should not silently defeat safety controls. Negotiated commercial access may increase a quota, but infrastructure rate limits and security checks can still apply independently.

Questions for your team

  • Store the approved contract reference.
  • Set explicit start and end dates.
  • Review overrides at renewal.
  • Test the effective plan after an override expires.

Frequently asked questions

Should custom access create a completely new plan?
Sometimes, but isolated overrides can be clearer for a small negotiated difference. Avoid cloning whole plans when only one term changes.

Keep reading

Launch your next pricing model this quarter.

Spin up a sandbox, send your first events, and see a finalized invoice before your next planning meeting.