Citrix named user licensing explained in one sentence: it assigns one license to a specific, identified person, who can then use Citrix from any device, anywhere, as often as they like. It is the simplest model to understand and administer, which is exactly why the vendor favours it and why buyers so often pay too much for it. As of 2026, with Cloud Software Group repricing renewals at widely reported increases of 50% to 200%, the choice to license by named user, and how many named users you actually buy, is one of the few cost levers fully inside your control. This article explains how the model works, where it overcharges, and how to right size it before a renewal locks the count in.
What named user licensing actually counts
A named user license is tied to a person, not a machine and not a session. Once a user is licensed, they can connect from a laptop in the office, a tablet at home, and a phone on the move, all under the same single entitlement, and they can connect as often as they wish without consuming anything additional. The license follows the human. You buy one for every named individual who needs access, and the total you pay is simply that headcount multiplied by the per user price.
This is genuinely convenient. There is nothing to measure at the moment of use, no session pool to monitor, no device inventory to maintain. An administrator assigns a user, and that user is covered everywhere. The convenience is real, and for some estates it is worth paying for. The problem is that the same convenience makes named user the easiest model for a vendor to grow, because the unit it counts, people on a directory, is large, visible, and almost always bigger than the number who actually use Citrix.
Named user licensing counts people, not usage. When those two numbers diverge, you pay for the gap.
How named user compares with device and concurrent
Citrix offers three counting models, and named user is only one of them. A device license is tied to a machine, so any person logging in from that device is covered, which fits shared hardware like clinical workstations or shop floor terminals. A concurrent license counts simultaneous active sessions, so a pool of licenses serves a much larger population as long as they are not all online at once, which fits shift and task based workforces. Named user sits between them in unit price but can be the most expensive in total, because it scales directly with headcount rather than with how that headcount behaves.
The comparison that matters is never list price per license, it is total cost for your estate, which is unit price multiplied by the quantity each model requires. Consider 5,000 staff where only 1,500 are ever on Citrix at peak because the rest work different shifts. Licensed per named user you buy 5,000 entitlements. Licensed concurrently you buy closer to 1,500 plus headroom. Even though each concurrent license costs more, buying a third of the quantity can make the total dramatically lower. Reverse the picture, an office of 2,000 people who all log in every morning, and named user wins, because peak concurrency nearly equals headcount and the simplicity comes free. The full comparison is set out in our guide to Citrix license types, user, device, and concurrent.
Where named user licensing overcharges
Named user is the wrong model whenever the people who could access Citrix substantially outnumber the people using it at any one time. Four patterns repeatedly trigger overspend. Shift based workforces, where a call center of 3,000 staff never has more than 1,000 online, pay for 3,000 named users when 1,000 concurrent would serve them. Shared device environments, where many people rotate through a smaller set of terminals, pay per person when device licensing would cover the same access for less. Seasonal or task based staff, who use Citrix briefly and intermittently, sit on full named user licenses for the whole term. And the most common pattern of all, licensing to headcount, where an organisation buys one named user license for every employee on the directory regardless of whether they touch Citrix at all.
That last pattern is the single largest source of Citrix overspend we see. Directories accumulate dormant accounts, departed staff who were never deprovisioned, service accounts, and duplicate identities carried over from acquisitions. Each of those inflates the named user count, and under a per user model each one is a license you are paying for and nobody is using. The model does not surface this waste, because it never asks whether the named user is active. It just bills the count.
How to right size your named user count
Right sizing named user licensing is a measurement exercise, and it runs in two stages. The first is cleaning the count. Reconcile your named user list against people who genuinely need access today, reclaiming dormant accounts, removing departed staff, eliminating duplicate identities, and stripping out service and test accounts that were never real users. This step alone routinely removes a meaningful share of the count, and it costs nothing but the work of looking. It is the same discipline that controls a license optimization exercise and a true up.
The second stage is testing the model itself. With a clean named user count in hand, compare its total cost against device and concurrent licensing using measured usage, not assumptions. Measure peak concurrent sessions across a representative period rather than an average, count the devices that are genuinely shared, and price each model against those real quantities. For many estates the answer is a mix: dedicated office users licensed per named user, shared terminals licensed per device, and a shift based operations floor licensed concurrently. The lowest cost compliant position rarely forces the whole estate onto one model, and identifying the segments is where the savings live. Getting peak concurrency right is the pivotal input, and it deserves the care described in our wider Citrix licensing fundamentals guidance.
Named user inside current Citrix packaging
Named user is a counting model, and counting models operate inside Citrix subscription packaging rather than alongside it. Since perpetual licensing ended in October 2022, Citrix is subscription only, and named user counts now sit within constructs such as the Citrix Platform license and Universal Hybrid Multi Cloud licensing. The deployment flexibility those packages add does not remove the counting question. You still choose how access is measured, and that choice still drives the quantity you buy. For how the subscription layer itself works, see our guide to Citrix subscription licensing.
One consequence of the move to subscription is that the named user count resets your cost base every term. There is no perpetual entitlement to fall back on, so an inflated count is not a one time purchase you can sweat, it is a recurring charge that compounds at every renewal and every true up. That makes cleaning the count before a renewal more valuable than it was under perpetual licensing, because the saving repeats rather than amortising away.
How the vendor steers you toward named user
The model decision is commercial, and the vendor has a clear preference. Per user counts are the largest and the easiest to grow, so current packaging and sales motions tend to present named user as the natural default and to frame concurrent or device alternatives as complex or unavailable. The framing is usually about simplicity, one license per person is easy to administer and easy to true up, and that convenience is genuine. But it is convenience the buyer funds, sometimes heavily, when the underlying usage is highly shared. As of 2026, some packaging changes under Cloud Software Group have narrowed concurrent availability for new purchases, which is itself a reason to confirm exactly what your agreement permits before assuming an alternative model is off the table.
The buyer side discipline is to treat named user as a number you defend with data rather than a default you accept. When you arrive at a renewal with a cleaned count, a measured concurrency curve, and a segmented view of the estate, the conversation shifts from the vendor's preferred headcount to the count your usage actually supports. That shift is where the leverage is, and it is the heart of our Citrix licensing advisory work.
Switching away from named user at renewal
A model choice is not permanent, and a renewal is the natural moment to revisit it. If your estate has grown more shared, or a workforce has moved to part time, remote, or shift patterns, the named user model that fit three years ago may now be the wrong one. The renewal is when you can re segment the estate and move groups to the model their current usage supports. The vendor will not propose this, because the profitable direction for them is the opposite, consolidating everyone onto a per user count. Bringing a re segmented proposal backed by fresh measurement is how you reset the model in your favour rather than drifting further into named user by default.
Switching does carry friction. Moving from named user to concurrent or device changes how you administer and report entitlements, and it can interact with support tiers and bundle terms. The friction is manageable, but it is a reason to plan the switch as part of a renewal project rather than attempt it mid term, where the contract usually offers less flexibility. The work pays for itself when the new model removes a quantity the old one was forcing you to carry every single year.
Common named user licensing mistakes
Three mistakes recur. The first is licensing to headcount instead of usage, buying one named user license for every employee on the directory whether or not they use Citrix, which is the largest and most avoidable source of overspend. The second is never cleaning the count, leaving dormant, departed, and duplicate accounts on the books year after year so each renewal and true up bills waste as if it were genuine demand. The third is accepting named user as the default without testing the alternatives against measured data, so a highly shared estate ends up on per user counts it does not need. Each mistake has the same root, deciding the model commercially without the usage data to support it, and the fix is always the same: measure first, clean the count, then price every model against the real numbers.
Frequently asked questions
What is Citrix named user licensing?
Citrix named user licensing assigns one license to a specific, identified person. That user can access Citrix from any device, anywhere, as often as they like, and the license follows them. You buy one license per named user regardless of how many devices they use or how often they connect.
When is named user licensing the wrong choice?
Named user licensing overcharges estates with high sharing or low simultaneous use, such as shift workers, shared clinical workstations, or seasonal staff. When many people rarely use Citrix at the same time, concurrent or device licensing usually costs far less, because named user counts scale with headcount rather than usage.
How do I right size Citrix named user licenses?
Reconcile your named user count against people who genuinely need access, reclaiming dormant, departed, and duplicate accounts. Then compare named user cost against device and concurrent models using measured usage. The right size is the count your real usage supports, not the number of people in the directory.
Is named user the default model under Cloud Software Group?
Named user counts are large and easy to grow, so current packaging and sales motions tend to favour them. As of 2026, with renewals arriving at steep increases, buyers should treat named user as a model to test against alternatives rather than a default to accept.
Can I switch away from named user licensing at renewal?
Often, yes. A renewal is the natural moment to re segment the estate and move groups to the model their usage supports. The vendor will not propose this, so bringing a re segmented, measured proposal to the table is how buyers reset the model in their favour.
For the full picture, see our Citrix licensing fundamentals pillar, and related guidance on Citrix license types compared and how Citrix subscription licensing works.