Policies
A Policy holds technical enforcement rules for licenses of a Product: grace periods, lease / heartbeat expectations, offline window clamps, and related backend limits. Policies pair with License Plans and FeatureLimits; they are not a substitute for entitlement codes.
Policy vs plan vs entitlements
| Layer | Role |
|---|---|
| Policy | How Runtime / Relay behave (timing, grace, offline clamps) |
| License Plan | Which commercial SKU / FeatureLimit set applies |
| License entitlements | Named grants on a specific license (copied into signed leases) |
Clients must not invent policy parameters locally. After activate, refresh, or offline issue, trust only the verified signed snapshot (Verify trust).
Console
Operations → Policies leads with the Policy name, availability for technical packaging, and the runtime outcomes it controls. A Policy detail groups bundle validity, offline grace/local lease, floating/borrow behavior, and the maintenance window before compatibility metadata. Exact codes, owner/source identifiers, and timestamps remain available under Advanced for support. Policy creation is shown only to operators with Policy management authority.
Vendors edit policy-related FeatureLimits on Product → Policy. Exact knobs ship with product modules — use Management OpenAPI for current request/response shapes (API Reference).
Modes that policies constrain
Policies often clamp behavior for modes described in Licensing Models: node-locked activations, floating checkout/heartbeat, offline lease TTL, trial expiry. Combining modes is normal; the signed lease carries the effective limits.
Related
- Plans · Products · Entitlements
- Offline / floating: Offline · Floating · Local Relay
- Core Concepts