-
Setup and onboarding
- Explore Adobe Admin Console
- Sign-in and access
-
Licensing
- Licensing overview
- Licensing types
-
Identity and SSO
- Set up identity
- Integrate with Microsoft Entra
- Integrate with Google Sync
- Integrate with other SSO providers
- Troubleshoot
-
Directories, domains, and access
-
Directories and domains
- Create a directory for SAML identity providers
- Verify domain ownership
- Set up domains for directory authentication
- Move domains across directories
- Encrypted and trusted directory domain transfers
- Move directories between Admin Consoles
- Delete directories and domains
- Automatic account creation overview
- Enable automatic account creation
- Automatic federated account creation FAQ
- Domain enforcement
- Directory trusting
-
Directories and domains
-
Settings
- Asset settings
- Manage encryption
-
User management
- Understand user management
- Manage users and groups
- Manage admins
- Manage user roles
- Migrate users
-
Products and entitlements
- Manage products
- Manage product profiles
- Special programs plans
- Manage entitlements
- Manage automatic assignment
- Manage product access
- Manage self-service policies
- Manage app integrations
- Frame.io integration
- Manage product permissions
- Manage storage and assets
-
Manage services
- Configure services
- Adobe Stock
- Custom fonts
- Adobe Asset Link
-
Deploy apps and updates
- Prepare for deployment
- Manage pre-generated packages
- Create packages
- Customize end-user experience
- Deploy packages
- Use third-party deployment tools
-
Manage Shared Device Licensing (SDL)
- Shared Device Licensing overview
- Deploy Shared Device Licensing
- Manage SDL profiles and user access
- Activate shared device licenses
- Use the Shared Device Licensing toolkit
- Recover shared device licenses
- Shared Device Licensing identity FAQ
- Shared Device Licensing deployment FAQ
- Shared Device Licensing access FAQ
- Known issues in Shared Device Licensing
- Adobe Update Server Setup Tool (AUSST)
- Adobe Remote Update Manager (RUM)
- Troubleshoot
- Contracts and renewals
- Reports and logs
-
Get started with Global Admin Console
- Get started
- Manage your organization
- Reports audit
-
Get help
- Support options
-
General troubleshooting
- Microsoft Purview Information Protection support in Acrobat
- Use the Creative Cloud Cleaner tool to fix installation issues
- Fix app launch errors on Shared Device Licensing machines
- Technical support boundaries for virtualized or server-based environments
- Resolve trial and license expired errors
- Migrating to OAuth Server-to-Server Credentials
- Manage device authentication for Creative Cloud and Acrobat Pro
Product profiles overview
Learn how product profiles control user access to Adobe apps and services in your organization.
Product profiles link products to users. Assigning a user to a profile gives them access to the related Adobe apps and services. You can create multiple profiles for one product, each with different settings, and assign different groups to each. This lets you match access to roles, departments, or teams.
Product profile functionality
Each product can have one or more profiles. A profile defines which services are available and sets usage limits. You then assign users or groups to that profile. Profiles serve as templates for everyone assigned to them. They also support delegation, allowing profile admins to manage user assignments without full system access.
Product profiles and entitlement
Entitlement refers to a user's right to access specific Adobe apps and services. Product profiles are the primary mechanism for granting these entitlements in enterprise and education organizations.
When you assign a user to a product profile, the Admin Console records that entitlement. The next time the user signs in with their credentials, Adobe's licensing system recognizes their access rights and grants them the apps and services defined in the profile.
A single user can be assigned to multiple product profiles across different products. The Admin Console tracks these assignments and ensures the user receives the combined entitlements from all their profiles.
Deployment considerations
Assigning users to product profiles grants them access but doesn't automatically install apps on their devices. You must create and deploy app packages separately using Named User Licensing or Shared Device Licensing methods.
For Named User Licensing, users install apps on their personal workstations and sign in with their credentials. The apps verify their entitlements against their assigned product profiles at launch.
For Shared Device Licensing, you deploy packages to shared devices in labs or classrooms. Users access the apps without individual sign-in, and licenses are managed at the device level.
The deployment workflow requires creating packages through the Admin Console and distributing them to end-user machines or shared devices using your organization's deployment tools.
Experience Cloud best practices
Organizations using Adobe Experience Cloud products should follow these limits for Admin Console performance:
- Maintain no more than 8000 product profiles across your entire organization
- Assign no more than 4000 product profiles to any single user
- Delegate no more than 100000 users to any single product profile
Going beyond these limits can slow down the Admin Console and make management more difficult. If you approach these limits, consider consolidating profiles with similar configurations or restructuring your user group strategy.
These limits apply to Experience Cloud products. Creative Cloud and Document Cloud products have different scaling characteristics.