Adobe Templates for Packages

Adobe Templates are pre-created Named User Licensing packages that are available for you to download from the Packages tab in the Admin Console. They are either single-app packages or collection packages created by Adobe. These packages are created based on default settings. You can choose to download packages based on the available Adobe Templates. You can also use the available templates as boilerplate to create packages.

Single-app packages also include the Creative Cloud desktop application-only package, which allows you to install the Creative Cloud desktop app.

View Adobe Templates

  1. Sign in to the Admin Console and navigate to Packages > Adobe Templates.

    The list of available templates is displayed.

    List of available Adobe templates

  2. Use the Search text box to filter the templates by Package name.

  3. By default, the list of packages is paginated with ten packages on a page.

    You can change the number of packages displayed on a page, by choosing from the drop-down list on the lower-right corner of the list of packages.

  4. To view the summary of a package, click anywhere on the row for a package in the list of packages.

    The package summary is displayed in the details drawer.

    Adobe template details

Download packages based on Adobe Templates

To deploy a package based on an Adobe Template, you must build and then download the package.

  1. To download a package, click anywhere on the row for a package in the list of packages.

  2. In the details drawer, click Download.

  3. You are navigated to the Packages page. When the build package procedure is over, the package is downloaded to your computer.

  4. To download the package later, click the package name in the list of packages and then click Download in the details drawer.


Packages that are based on Adobe Templates for non Creative Cloud apps such as Captivate, Framemaker, RoboHelp, do not include the Creative Cloud Desktop Application.

Customize and download packages based on Adobe Templates

An Adobe Template provides you with the boilerplate applications and configurations as defined by the template. When creating a package, you can choose to create the package from scratch. Alternatively, you can find the Adobe Template that comes closest to matching your requirements and use it as the starting point.


When you customize a template, you can add products that are part of Creative Cloud or Document Cloud. Alternatively, you can add products of Adobe Technical Communications Suite(TCS)—Adobe Captivate, RoboHelp, FrameMaker, and Presenter—that are not part of either of the clouds.

The template that you customize with the products of TCS, does not provide all the customization options available in the template for Creative Cloud apps.

  1. To customize a package based on an Adobe Template, click anywhere on the row for a package in the list of packages.

  2. In the details drawer that opens, click Customize.

  3. On the Configure screen, select or enable the required options:

    • Platform (Windows only): Choose the processor support.

    It's necessary to create separate packages for Windows 64-bit and Windows ARM devices. A package made for one architecture type, cannot be deployed on another.

    • Language: Select the language in which you want to create the package.
    • Use OS Locale: Enable to create a package that deploys in the OS language of client machine. In which case, the OS language is the default fallback language in which the package is deployed.

    When you're done, click Next.

  4. The Choose Apps screen allows you to add or remove applications that were defined in the Adobe Template.

    Choose apps

    Select the Show older versions check box to display the list of supported previous versions, if any.

    After you have added the applications to include in the package, click Next.

  5. (Not currently available for Windows ARM or macOS (Apple Silicon) devices) On the Choose Plugins screen, search and select plugins to include in the package, and click Next.

    You can select the Show Compatible Plugins Only check box to display the plugins that are compatible with the apps in the package. This filter doesn't appear if you only have the Creative Cloud desktop app in your package.

    To view the list of selected plugins, click Selected Plugins.


    The plugins that you include in the package do not necessarily need the supporting application to be part of the same package. You can include plugins and extensions for apps that are previously installed on your users' computers. Also, if a computer does not have the targeted application for a plugin, the plugin is not installed on the computer.

    Choose plugins

  6. On the Options screen, select or enable the required options and then click Next.

    Customize Template options

    Creative Cloud Desktop Options:

    • Enable self-service install: Allow users to install and update applications from Apps panel in the Creative Cloud desktop app. Learn more.
    • Allow non-admin to update and install apps: Enable self-service for end users who do not have administrative privileges, to install, and manage their applications and updates. Learn more.
    • Disable auto-update for end users: Ensure that end users will not be able to automatically update their applications via the Creative Cloud Desktop app. Learn more.
    • Enable self-service plugin install: Allow end users to install and update plugins from the Marketplace tab in Creative Cloud desktop app. If deselected, the users can't browse or install any plugins using the Creative Cloud desktop app. Learn more.
    • Disable file syncing: Suppress the automatic syncing of files to client systems. Useful when you are installing packages in a test environment where you want to suppress file syncing. Read more on disabling file syncing. This option is available for Creative Cloud subscribers in commercial and educational organizations only. It is not available for subscribers in government organizations.
    • Enable browser-based login: By default, users must sign in using the Creative Cloud desktop app. Choose this option to redirect users to sign in via the browser. Learn more.
    • Enable install of beta apps: Enables end users to install and update beta apps from the Creative Cloud desktop application. This means that end users can then go to the Creative Cloud Desktop application and install or update these apps. Learn more.

    Also read about other customization options, in Creative Cloud app & services | Customizations.

    Management Options:

    • Enable Remote Update Manager: Enables the use of Remote Update Manager. Adobe Remote Update Manager lets you remotely run the updater on the client with the benefit of executing as an administrator. Learn more.
    • Redirect to internal update server: Enables you to redirect all updates for this package to an internal update server. The internal server details are specified in an override XML in the Packages > Preferences tab of the Admin Console. Learn how to set the Preferences.
    • (Not currently available for Windows ARM or Apple Silicon devices) Create a folder for extensions & include the Adobe Extension Manager command-line tool: This option is enabled if you have plugins in the package. It creates a subfolder in the package folder to include extensions to install with the package. For more, see Manage Extensions in packages.
      • Include Adobe Asset Link: (Available if the above option is switched on) This extension connects Adobe Experience Manager (AEM) Assets with Creative Cloud desktop apps Photoshop, Illustrator, and InDesign. 

    Note: AEM Assets is required. For details, see Adobe Asset Link. This feature is only available for Creative Cloud for enterprise customers.

    • Install package to custom  install directory: Enables you to install the apps in this package to a custom install directory. The directory is defined in the Packages > Preferences tab in the Admin Console. Learn how to set the Preferences.
  7. On the Finalize screen, enter the name of the package, review the package details, included applications, and plugins. Then, click Build Package.

    Finalize package

    It displays a message after the build process completes. If the package is built successfully, the message also indicates the time period for which the package is available for download from the Admin Console.

    If you want to check the remaining time for the existing packages in the details pane, click the row item for the package.

  8. To download the package later, click anywhere on the row for a package in the list of packages and then click Download in the details drawer.

  • If you are creating macOS packages, the Adobe Package Downloader is downloaded to your computer. Open and run to complete download of package. For further details, see here.
  • If you create a package that includes Captivate 2017 or Presenter (any version), you must first uninstall these product versions on the end-user computers before you deploy this package.

Next Steps

Deploy packages

After you create the package, choose from the following methods to deploy the package:

  • Use third-party tools such as Microsoft System Center Configuration Manager (SCCM), Apple Remote Desktop, or JAMF Pro for remote deployment. Learn more.
  • Install by double-clicking the package file. Learn more.
  • Deploy using command line on Windows computers. Learn more.
  • Deploy using Info.plist file on macOS computers. Learn more.

For information on how to deploy updates, see Change management for Adobe enterprise and teams customers.

Adobe logo

Sign in to your account