Adobe FRL and Shared Device Licensing Explained

Two licensing models, two different problems

Named user licensing is Adobe's default, and for most knowledge workers it is the right model. But it is a poor fit for two common situations: locked down environments with no internet access, and shared machines used by many people. Feature Restricted Licensing and Shared Device Licensing exist to serve those cases, and using them correctly can take real cost out of an estate.

The mistake buyers make is paying for named user seats in environments where one of these alternatives would cost far less.

Feature Restricted Licensing

Feature Restricted Licensing, often shortened to FRL, is built for secure or air gapped environments where named user sign in is not possible. It activates the software without requiring each user to authenticate, at the cost of certain online and storage features. For regulated, classified, or isolated networks, FRL is frequently the only workable model, and it removes the need to buy and manage full named user seats for machines that could never use the online features anyway.

If you run secure environments and you are paying full named user pricing for them, that is a flag worth raising at your next review.

Shared Device Licensing

Shared Device Licensing assigns the entitlement to a machine rather than to a person. It is designed for shared spaces such as labs, classrooms, training rooms, and shift based workstations where many different people use the same device. Instead of buying a seat for every individual who might sit down, you license the device, which can be dramatically cheaper when the user to device ratio is high.

It is widely associated with education, but any organization running shared workstations should evaluate it.

Choosing the right model

The decision comes down to the environment. Use named user for individual knowledge workers, Feature Restricted Licensing for secure or disconnected machines, and Shared Device Licensing where many people share a smaller number of devices. Most large estates have pockets of all three, and the saving comes from matching each pocket to the cheapest model that still meets the need.

FRL and Shared Device Licensing are not loopholes, they are standard Adobe models that simply go underused because they are poorly understood. Map your environments honestly, place each one on the model that fits, and you will stop paying named user prices for machines and spaces that never needed them.