The short answer to what is a named user license: it is an entitlement tied to one specific identified person who can access the software whenever they like, so one license equals one named individual no matter how often that person actually uses it. In Citrix, the named user license is one of the three core counting models alongside device and concurrent, and choosing it correctly is one of the largest cost decisions in your estate. As of 2026, current packaging tends to push buyers toward per user counts, which makes understanding what you are really buying more important, not less.
What the term means
A named user license attaches an entitlement to a person, not to a moment of activity or a piece of hardware. Once assigned, that individual holds the right to connect at any time, and the license stays reserved for them whether they use it daily or twice a year. To stay compliant you need one named user license for every individual who could log in, which means the count follows your headcount rather than your usage. The model trades efficiency for simplicity: it is easy to administer and forecast, because every person maps to exactly one license, and that predictability is its main appeal.
A named user license bills the size of your roster, not the size of your activity. The gap between the two is where you overpay.
Where it appears in your agreement
Named user counts show up wherever your order documents specify a user based metric, and in current packaging they are frequently the default model inside subscription constructs such as the Universal Hybrid Multi Cloud license or a Platform level package. Because perpetual licensing ended in October 2022, named user entitlements today are subscription based and counted at each renewal and true up. Your agreement will state the metric explicitly, and it matters because moving between named user, device, and concurrent models is far easier to plan before signing than to unwind afterward.
How it is used for or against you
For the buyer, named user licensing is the right answer when usage is dedicated, such as finance teams, developers, or back office staff who each use Citrix on their own assigned identity throughout the day. In that profile, peak activity is close to headcount, so there is little to gain from a shared model and the administrative simplicity is worth having. Against the buyer, the risk is applying the named user model to a highly shared estate. Shift based contact centres, seasonal workforces, and rotating clinical staff all have far fewer people active at once than on the roster, so paying per named user means paying for licenses that sit idle most of the time. The vendor benefit is clear, since named user counts are the largest and easiest to grow, which is why the discipline is to test every model against measured usage rather than accept the per user default.
Related terms and guidance
A named user license is best understood against the alternatives, so see our full comparison of Citrix license types, user, device, and concurrent and our detailed explainer on Citrix named user licensing. It contrasts directly with the concurrent model. For the full picture, see our Citrix licensing fundamentals pillar, and return to the full Citrix licensing glossary for more definitions.
Frequently asked questions
What is a named user license?
A named user license is an entitlement tied to a specific identified person who may access the software whenever they like. One license equals one named individual, regardless of how often or how little they actually use it. In Citrix, named user licensing is one of the user, device, and concurrent counting models.
How is a named user license different from a concurrent license?
A named user license is assigned to one person permanently, so you need one for every individual who could log in. A concurrent license is shared from a pool and counts only simultaneous active sessions, so a smaller number can serve a larger population. Named user counts headcount, concurrent counts peak activity.
When does named user licensing cost more than it should?
When usage is highly shared, such as shift based or task based populations, because you pay for every named person even though only a fraction are ever active at once. As of 2026, current packaging tends to steer buyers toward per user counts, so highly shared estates often overpay unless they test concurrent or device models against measured usage.
Why does Citrix favour named user licensing?
Named user counts are the largest and the easiest to grow over time, so they generate more revenue and are simpler to true up. The vendor frames the model as easy to administer, which is true, but that convenience is something the buyer pays for whenever real usage is shared rather than dedicated.