Skip to main content

Windows and precedence

Assignments and entitlements often have effective windows and precedence rules.

This page describes precedence rules used to derive effective runtime behavior.

Effective-window rule​

An assignment is effective at time T only when all are true:

  • assignment status is active
  • window_start <= T
  • window_end is null or window_end > T
  • referenced plan is active

For gate bundle resolution, only plans of kind base and addon participate.

Bundle precedence​

When multiple effective assignments provide bundle candidates:

  1. Resolve candidate bundle keys from billing_plans.metadata.gate_bundle_key.
  2. For the same bundle key, keep the highest-priority plan.
  3. Across remaining candidates, select highest plan priority first.
  4. First candidate with an active bundle wins.

Account-scoped assignments can contribute account-scoped and user-scoped gate policies. User-scoped assignments only contribute user-scoped gate policies for that billing user.

Planning guidance for overlapping windows​

  • Keep one base plan effective at a time whenever possible.
  • Use add-on plans for incremental access.
  • Model scheduled plan switches with non-overlapping windows where practical.
  • Prefer explicit cancellation/end windows over implicit replacement.

Verify​

  • For overlapping windows, you can predict which plan is effective.
  • Your support team can explain why a customer received a given decision.

Next​