If the license type of your organization changes, to continue working your end users will need to sign out of any Adobe product or service and then sign back in with the same credentials.
For desktop products such as Photoshop, Acrobat, Illustrator, use the Sign out and Sign in options in the Help menu. On Adobe.com, use the icon in the upper-right corner to sign out and then sign back.
Named user licensing is the default and most popular licensing method to deploy and use Adobe Creative Cloud and Document Cloud products. Designed for the network-connected scenario where app licenses are managed based on individual user need for use of the app. Using named user licensing, you can provide your end users with the full functionality of the software and services. Giving your end-users access to all the available apps and services based on your organization's entitlements.
Named User Licensing ties the usage of Adobe apps and services to an individual user. It works well if the product and service requirements are closely associated with a user or a role. Named User Licensing provides IT admins complete control to add and remove product licenses for a user at any time. It also facilitates better compliance tracking as IT admins don't need to track machines, and can manage licenses centrally.
Named licenses require periodic Internet connectivity. Computers must connect to Adobe servers for initial activation, and then at least once every 99 days. End users cannot use mobile apps unless the company deploys named licenses.
End users can sign in with their credentials to access the apps and services. You can also configure SSO to enable seamless access and experience as the rest of your enterprise apps.
Named User Licensing, provides:
For end users:
- Access to World-class creative & productivity apps: Including the latest cloud first applications such as Adobe XD, Lightroom CC and Adobe Dimension. These applications are not available with any other licensing method, including Feature Restricted Licensing.
- Access to Adobe Cloud services: Jump-start projects with anywhere, any-device access to assets in Creative Cloud Libraries, cloud collaboration using Team Projects, and font collections from Adobe Fonts. Automate signature driven workflows and deliver a faster return on signed documents with Adobe Sign.
There is no requirement to pre-configure computers for Named User Licensing. Creative Cloud apps will only need to be installed or deployed on the end-user computers. Each of the computers to be licensed must have access to the Internet. However, access to the Internet can be controlled by a firewall device that intercepts and unpacks all network traffic to verify its content and ensure that:
- no unauthorized data is sent outside the internal network
- all transmitted data is sealed inside an encrypted tunnel between the firewall device and the Adobe servers
- the endpoint of every transmission is an authorized Adobe server with a known network address and a publicly signed, non-revoked SSL certificate
Apps can be downloaded and installed on client machines using various methods. For information, see App delivery strategies. Users need to sign in to license the apps. To license the apps, users can use one of the following:
Creative Cloud app for desktop
The Creative Cloud app for desktop facilitates self-service workflows for users to download and install applications and updates. For users with the cloud services, signing in also enables access to Creative Cloud services, such as activate fonts from Adobe Fonts, get personal storage, and share and gather feedback on Behance.
Directly from apps
On launching an app, a sign-in screen displays. End users can sign in with their credentials to license the app. If a user is not entitled to that particular app it will run as a trial, but will stop working once the trial period expires.
To ensure that users are able to sign in, you'll need to configure your firewall and proxy servers to enable connections to the web service endpoints on the Adobe website.
For a detailed list of licensing and other service endpoints, see Creative Cloud for enterprise - Network Endpoints.
A licensing model recommended for highly secure environments, such as government organizations. It is recommended for organizations that have very specific needs to control data flow in and out of locked down or restricted network environments. Use this licensing model for end users who either don't have access to the internet or are not allowed to use online services. Note that FRL restricts access to certain Adobe apps and services for your end users.
The FRL licensing method is not part of all organization agreements for enterprise accounts with Adobe. You need to verify if it part of your organization's agreement.
Use Feature Restricted Licensing (FRL) when your end users either do not have access to a network environment or are not allowed to use online services.
FRL packages are best suited for the following end-user environments:
- a kiosk-style configuration where individual users do not log in
- an isolated (off-network) secure facility
Only app versions CC 2019 or later support licensing via FRL.
Named User licensing helps you realize best value of your investment in Adobe apps and services. However, if your organizational setup so requires, you may use Feature Restricted Licensing model to deploy apps. If you use FRL packages to deploy apps, users will not have access to the certain apps and services that may be included in your organization's agreement with Adobe.
For example, your end users will not have access to any Adobe Cloud-first services. Also, your end users won't have access to several Cloud-first apps. For example:
A historical method of licensing that is not tied to an individual user but to a particular computer. This licensing method is suitable for a very small number of customers and, as with named licensing, can be used to create pre-licensed packages that are deployed remotely.
App versions CC 2019 or later do not support licensing via serial numbers. For more information, see this document.
Named licensing provides several advantages as compared to anonymous or Serial number licensing. Administrators can closely track and monitor the usage of licenses. They can also centrally manage licenses assigned to a user and revoke access to apps and services, without a need to redeploy packages. Named license can also enable self-service workflows to let customers download and install products and updates. Named licenses also enable end users to use cloud services, such as add fonts from Adobe Fonts, choose file sync locations, and share and gather feedback on Behance.
If you have an existing CS6 or Creative Cloud ELA/ETLA or VIP deployment, you can consider migrating users to the Named licensing mode.
To prevent disrupting end-user workflows, invite users to your organization, and add them to groups to assign licenses. This will give users some time to accept the invitations and set up their IDs. You can also inform users that they'll need to sign in to use the apps.
Create and deploy a package that includes the Creative Cloud app. This package can contain only the Creative Cloud app or be bundled along with other Creative Cloud applications. Deploying the latest version of Creative Cloud app updates the necessary files for using named licenses.
To download this package directly from the Admin Console, navigate to Packages > Adobe Templates. You can also create it using the Creative Cloud Packager.Step text
To remove enterprise license of previously licensed apps, run the RemoveVolumeSerial executable with admin privileges.
RemoveVolumeSerial file deactivates all Creative Cloud for enterprise products running on a client's machine, irrespective of the serial number specified when creating the RemoveVolumeSerial file.
For example, if you create a RemoveVolumeSerial file using the serial number 1234-1234-1234-1235, and deploy it on a machine which is using the serial number 1234-1234-1234-1236, all Creative Cloud for enterprise products running on the machine are deactivated.
Package and deploy latest versions of apps and updates. Use Admin Console or the Creative Cloud Packager to create a package with a Named License. For more information, see Creative Cloud Packager. Skip this step if you don’t want to update to the latest versions of apps.
If you want to uninstall the older versions of apps, do it before you deploy the latest versions. Uninstalling later may break file associations.
If serial number licenses have been made available to your enterprise, you can obtain these from the Adobe Licensing website website.
For more help, see Using Adobe Licensing Website (LWS)..
Adobe Licensing Website does not support Enterprise IDs. If you're planning to use serial number licensing, we recommend that all administrator accounts be set up using Adobe IDs.
Device licenses allow institutions enrolled in the Value Incentive Plan (VIP) to license software to a specific computer. Also, users never have to sign in or enter a serial number to access apps.
App versions CC 2019 or later do not support device licensing. For more information, see this document.
Creative Cloud for education device licenses provide the ability to license software to a specific machine instead of a named user or with a serial number. Users never have to sign in or enter a serial number to use the software. Licenses are tied to machine deployment pools, which are created automatically when you order products.
If your institution has purchased device licenses, learn how to manage device licenses in the Admin Console. You can also learn how to create packages with device licenses using Creative Cloud Packager.