Group name
Last updated on
Aug 3, 2026
Plan deployment packages by mapping user groups to their application needs before creating packages in Adobe Admin Console.
User group and app deployment details
Each user group with unique requirements needs its own deployment package. Identify the following details for each group:
- Group name: Labels that clearly identify each user group are for internal use only and don't appear in deployment packages.
- Primary applications: The applications required by each group.
- Product identification: The products that provide those applications, including individual products and suite products.
- Platform requirements: The platform each product runs on: Windows, macOS, or both.
After identifying user groups, define package details based on their requirements.
Package details
Determine your package count and package details during package design:
Package count | Your package count is 1 package if using a single platform and 2 if supporting both Windows and macOS. |
Package name | Use a short, descriptive name. If both platforms exist, use a common name and append Windows or macOS to easily identify them. |
Note
Package names become folder names on your system, so the same naming constraints apply.
Deployment planning sheet
Use this planning sheet to map your user groups and package details.
|
|
Primary applications needed |
Platforms |
Package count |
Package name(s) |
|
Writers |
InDesign |
Windows (64-bit) |
1 |
InDesign-only |
|
Photographers |
Photoshop |
macOS Windows (32-bit) |
2 |
PhotoMac |
|
Layout team |
Photoshop, Illustrator, InDesign |
macOS |
1 |
Layout |
|
Web Makers |
Dreamweaver, Adobe XD |
macOS Windows (32-bit) |
2 |
WebMac |
