Sign in to the Admin Console and select Packages > Packages.
Last updated on
Aug 3, 2026
Learn how to create Self-service packages that allow users to install and update Adobe applications without administrative privileges.
Named user licensing supports two deployment methods for network-connected environments: Self-service and Managed packages. Self-service packages let users install and update Creative Cloud and Document Cloud applications through the Creative Cloud Desktop app. If your users don't have administrator credentials, create a Self-service package to give them control over the Adobe applications and updates they can install.
Before you begin
Packages cannot be deployed across different operating systems or architecture types.
Create separate packages for Windows 32-bit, Windows 64-bit, Windows ARM, macOS (Intel), and macOS (Apple Silicon) devices. Alternatively, use a macOS (Universal) package for both Intel and Apple Silicon devices.
Build Self-service packages
Select Create a package.
Choose Self-service package and select Next.
Enter a package name in the Package name field.
Select your target platform from the Choose a platform drop-down menu:
- macOS (Universal)
- macOS (Intel)
- macOS (Apple Silicon)
- Windows (64-bit)
- Windows (32-bit)
- Windows (ARM)
Note
If you choose a macOS platform, you can create flat packages. This option is selected by default.
Configure the package options as needed, and then select Create package.
After the package build completes, select the package from the Packages list to check its availability.
Select Download for the required package, then choose a location to save the package in the Save As dialog box.
If you double-click a downloaded package ZIP file on macOS 10.14 or earlier, you may encounter an Unable to expand error. This is because the macOS Archive Utility does not support unzipping large files created with Zip64 mode. To extract the package, open Terminal in the download folder and run unzip <file_name>.zip.
Package options
|
Option |
Description |
|
Language |
The language in which the package is created. |
|
Use OS Locale |
Deploys the package in the operating system language of the client machine. The OS language is the default fallback language in which the package is deployed. |
|
Create a folder for extensions & include the Adobe Extension Manager command-line tool |
Creates a subfolder in your package folder for installing extensions with the package. Not available for Windows ARM devices. |
|
Redirect to internal update server |
Redirects all package updates to an internal update server. Server details are specified in an override XML in Packages > Preferences tab of the Admin Console. |
|
Enable install of beta apps from the Creative Cloud Desktop application |
Allows end users to install and update beta apps from the Creative Cloud Desktop app. Learn more about how to customize Creative Cloud app settings. |
Caution
If the package that you've created contains one or more revoked apps, the status displays as Revoked. Also, you cannot download this package.
Packageinfo.txt
The downloaded package includes a PackageInfo.txt file with details about the package configuration. This file is for informational purposes only.
|
Package Name |
|
Package Type – Self-service or Managed |
|
Platform |
|
Locale |
|
Creative Cloud Desktop app version |
|
Package Configurations
|
Note
Using the Creative Cloud Desktop app, your end users can install only the two most recent major versions of Creative Cloud apps. For end users who require older versions, create and deploy Managed packages.
