Deploy Shared Device Licensing

Shared Device Licensing is designed for labs, classrooms, libraries, and other shared environments where multiple users access Adobe applications on the same device. Deploying Shared Device Licensing involves configuring identity management, user access, deployment packages, product profiles, and deployment methods before distributing applications to shared devices.

Step 1: Setup identity and user management

Configure identity management to enable Enterprise ID or Federated ID accounts for shared device users.

To complete identity setup, organizations must demonstrate ownership of the associated domain. This process may require assistance from teams responsible for managing organizational websites or email services.

Adobe recommends using Enterprise ID or Federated ID accounts for students and lab users because these identity types provide better organizational control and monitoring.

Step 2: Assign administrative roles and access

The primary administrator in Admin Console is the System admin, who has permission to perform all administrative tasks.

Organizations can assign additional administrative roles to distribute responsibilities across deployment teams.

Available administrative roles include:

• Product admins, who can create product profiles and add users to the organization
• Product profile admins, who can manage assigned product profiles and add users to the organization

Step 3: Add users to the Admin Console

If you plan to configure shared devices to be accessible by Organization users only, you must add these users to the Admin Console.

You can add users using any of the following methods:

• Manually adding users one at a time
• Bulk uploading users using a CSV file
• Setting up the User Sync Tool (recommended for large organizations).

Step 4: Create deployment packages

Use the Packages tab in Admin Console to create Shared Device Licensing deployment packages.

Step 5: Create product profiles

Organizations deploying applications across multiple labs or shared environments can create separate product profiles for different deployment requirements. Some examples are:

• Unrestricted labs allow access for all users
• Restricted labs limit access to organization users only

Access behavior can also be controlled using policies configured for individual product profiles.

Step 6: Define shared device access policies

Shared device configurations provide three ways to control user access to applications on shared devices.

Organizations can configure:

• Access Policy
• Egress IP
• Associated Machines

These controls help prevent unauthorized application usage and protect organization-managed accounts and assets.

Organizations can apply a combination of these policies depending on deployment and security requirements.

Configure shared device access settings using shared device configuration. 

Step 7: Deploy packages to shared devices

After creating deployment packages, organizations can deploy packages to shared devices across labs, classrooms, libraries, or other shared environments.

Organizations can deploy packages using third-party deployment tools such as:

• Microsoft SCCM
• Apple Remote Desktop
• JAMF Pro
• Munki
• Microsoft Intune

Packages can also be deployed in the following ways:

• Running the package installer directly
• Using command-line deployment workflows on Windows devices
• Using Info.plist configurations on macOS devices