Understand how licenses authenticate Adobe software and control product access for your organization.
When you purchase Adobe products, you acquire licenses that govern how your organization and its users access Adobe software and services. They represent your legal right to use Adobe products and authenticate them on end-user devices.
Licensing shapes how you provision software, manage access to cloud services, deploy packages, track usage, and control administrative settings.
Adobe licensing overview
A license authenticates and activates Adobe products on computers or devices. When you purchase Adobe products, your contract specifies the number of licenses, which must be assigned to users or devices before they can access software and services.
Your licensing method determines how licenses connect to users or devices. Some licensing types tie to individual user identities, enabling personalized experiences and cloud service access. Other types assign licenses to shared devices, allowing multiple people to use the same installation without individual accounts.
Named User Licensing
Named licensing provides access to Adobe-hosted services. It allows centralized license and compliance management through the Adobe Admin Console. It offers flexibility, letting users switch between product profiles over time. It supports self-service workflows, allowing users to install apps and updates themselves. The Admin Console also provides automatically created packages, based on default settings and purchased products, which can be downloaded and deployed directly. Learn more about deploying apps and updates.
Shared Device Licensing
Shared Device Licensing assigns licenses to devices rather than individuals. Anyone who signs in to a licensed device can access the installed Adobe products. This method works well for educational institutions with computer labs and classrooms where multiple students and teachers share the same equipment.
When you deploy software using Shared Device Licensing, the device itself consumes the license. Users don't need individual Adobe accounts to use the software, though they may need institutional credentials to access the device. This approach simplifies management in environments with high user turnover and shared computing resources.
