Set entitlement policies

Policies decide how an entitlement may be activated and for how long. You set them on an entitlement’s Policies tab (or capture them in a template so every grant inherits them). They combine — a grant can be, say, a subscription with floating seats and a trial.

Seat allocation

How many devices or users may run at once, and how a seat is held.

• Fixed vs. floating seats — fixed pins a seat to a device; floating lets devices take and release seats from a pool.
• Lease — how long an activated session is valid before it must check in to renew.
• Offline grace — how long a device may keep running past its lease without connectivity before the license stops honouring it.

To change the seat count on a live entitlement, use Add Seats / manage quota rather than editing the policy from scratch — see Renewals, credits & activations.

Trial

A trial window that can start on grant or on first activation. Pair it with a subscription so a customer rolls from trial to paid. While in trial, the entitlement’s subscription status reads Trialing.

Time-restricted

Valid between two dates, or for a fixed period after first use. Good for time-boxed licenses, evaluations and event passes. Outside the window the license is Expired.

Subscription

Recurring periods with renewal and expiry. The subscription status (Active, Paused, Expired, Canceled) is computed from these dates and surfaced on the entitlement; renewals extend the current period — see Renewals, credits & activations.

How policies show up at runtime

Policies don’t act alone — they’re snapshotted into the session at activation, alongside the entitled features and the applied plan. The running license carries its own lease, trial and grace bounds, and the device checks in to renew the lease and checks out to release a floating seat. See Activation & sessions for the device side.

Next

• Issue the grant → Author & publish entitlements
• The model in depth → Entitlements & templates