Adobe app deployment overview

Last updated on Nov 4, 2026

Learn about the package types and deployment strategies for delivering Adobe apps and updates to your organization.

Packages you create in the Adobe Admin Console decide which app versions your users get, when updates arrive, and how much users can change. Your choice affects admin workload, user experience, and network bandwidth.

To get started, sign in to the Adobe Admin Console with your administrator account, then select Packages.

Choose a deployment method

If you need to…	Use this method	What it does	Next step
Let users install apps and updates themselves with the least setup	Self-service (no package)	Users download the Creative Cloud desktop app from Adobe. You assign licenses (Teams) or product profiles (Enterprise).	Product profiles and license assignment
Put the Creative Cloud desktop app on user machines for them	Self-service package	The package includes the Creative Cloud desktop app. Users choose their own apps and updates.	Create Self-service packages
Cut internet bandwidth and hold updates until you release them	Self-service or managed package with AUSST	Apps and updates come from your internal update server instead of Adobe.	Adobe Update Server Setup Tool overview
Give everyone the same apps and versions, or work on a restricted network	Managed package	You choose the apps and versions. Users install from the package.	Create Managed packages
Decide exactly when updates install	Managed package with Remote Update Manager (RUM), or an update-only package	You run the updater on client machines remotely, or push updates as a package.	Deploy and manage updates with RUM
Install on shared computers such as labs or kiosks	Shared Device Licensing (SDL) package	One license covers unlimited users on a configured machine.	Create Shared Device Licensing packages
Install an earlier app version	Managed package	Choose the version on the Choose apps screen.	Create Managed packages
Remove apps and licenses	Uninstall package	Removes Creative Cloud products and their licenses from user machines.	Uninstall Creative Cloud apps
Deploy Acrobat only	Acrobat-only package	Packages Acrobat without other Creative Cloud apps.	Create Acrobat-only packages

Not sure which to pick? Adobe doesn't set a single default for every organization. Trade admin effort against control: self-service is the easiest to run; managed packages with AUSST give you the most control. Test any package on a pilot group before you roll it out (Test packages before deployment).

Choose your licensing type

Your licensing type decides which package types you can use.

Named User Licensing. The license follows the user to any machine they sign in to. Use any method in this article except SDL packages. Named User Licensing overview
Shared Device Licensing. The license stays with the machine, so many users can share it. Use it for shared computers, not for machines with a dedicated user. Deploy it with an SDL package. Shared Device Licensing overview · Deploy Shared Device Licensing

Compare self-service and managed packages

Adobe delivers updates, new features, and app versions as they become available. Compare the five approaches below. Admin control and ease of deployment are rated from 1 (least) to 5 (most).

	Self-service (no package)	Self-service package	Self-service package with AUSST	Managed package	Managed package with AUSST
How users get apps and updates	Users download the Creative Cloud desktop app from Adobe and install apps and updates with it.	Users install the Creative Cloud desktop app from the package, then install apps and updates with it.	Users install apps and updates with the Creative Cloud desktop app, served from your internal update server.	Users install apps and updates from the package.	Users install apps and updates from the package.
License type	Named User Licensing (Enterprise or Teams)	Named User Licensing (Enterprise or Teams)	Named User Licensing (Enterprise or Teams)	Named User Licensing. For Shared Device Licensing, use an SDL package.	Named User Licensing. For Shared Device Licensing, use an SDL package.
Best for	Diverse, changing app needs. Smallest footprint on machines.	Same as self-service.	Same as self-service, plus lower internet bandwidth use and tighter control over updates.	Restricted environments with limited web access. The same app versions for every user, for file compatibility. Lower internet bandwidth use.	Same as managed, plus tighter control over updates.
App versions available	Latest apps and previous major versions in the Creative Cloud desktop app. See the Creative Cloud Support Policy.	Same as self-service.	Same as self-service.	Versions you select in Packages in the Admin Console.	Versions you select in Packages in the Admin Console.
Requires	Administrative privileges and an internet connection on user machines.	An internet connection on user machines.	An internal update server with an internet connection.	A dedicated IT admin.	An internal update server and a dedicated IT admin.
How you deliver updates	Users update from the Creative Cloud desktop app.	Users update from the Creative Cloud desktop app.	Users update from the Creative Cloud desktop app, using your server.	Create an update-only package, or run Remote Update Manager to deploy updates from Adobe.	Create an update-only package, or run Remote Update Manager to deploy updates from your internal update server.
Admin control (1–5)	1 (least)	2	3	4	5 (most)
Ease of deploying (1–5)	1 (easiest)	2	3	4	5 (hardest)

With self-service, the Apps panel in the Creative Cloud desktop app is always on. With managed packages, users install packages by default. To let them install and update apps from the Apps panel as well, turn it on when you build the package. See Customize using managed packages.

Control updates

You have three ways to control when and where updates reach users.

Update-only packages. Build a package that contains only updates and deploy it on your schedule. Deploy updates overview
Remote Update Manager (RUM). Run the updater on client machines from the command line. Select Enable Remote Update Manager on the Options screen when you create a managed package. RUM overview · Deploy and manage updates with RUM · RUM syntax and log reference
Internal update server (AUSST). Host updates on your own server. Select Redirect to internal update server when you create a package. Configure an internal update server for packages

RUM works with managed packages. It doesn't apply to self-service deployments.

Install earlier app versions

Self-service users get the latest apps and previous major versions. If you need a specific earlier version, build a managed package and pick the version on the Choose apps screen. Versions are subject to the Creative Cloud Support Policy, and a package that contains a revoked app version can't be downloaded.

Some current app versions require a processor with AVX2 support. Check system requirements before you deploy to older hardware.

Join the Community

Use our Enterprise and Teams Community to ask questions, collaborate with other admins, and stay informed about new features.

App deployment planning

Learn

Learn with step-by-step video tutorials and hands-on guidance right in the app.

Community

Join discussions, find answers, learn from experts, and share your knowledge.

Adobe Home

Access your favorite Creative Cloud apps, services, file management, and more.