- Adobe Enterprise & Teams: Administration guide
- Plan your deployment
- Basic concepts
- Deployment Guides
- Deploy Creative Cloud for education
- Deployment home
- K-12 Onboarding Wizard
- Simple setup
- Syncing Users
- Roster Sync K-12 (US)
- Key licensing concepts
- Deployment options
- Quick tips
- Approve Adobe apps in Google Admin Console
- Enable Adobe Express in Google Classroom
- Integration with Canvas LMS
- Integration with Blackboard Learn
- Configuring SSO for District Portals and LMSs
- Add users through Roster Sync
- Kivuto FAQ
- Primary and Secondary institution eligibility guidelines
- Set up your organization
- Identity types | Overview
- Set up identity | Overview
- Set up organization with Enterprise ID
- Setup Azure AD federation and sync
- Set up Google Federation and sync
- Set up organization with Microsoft ADFS
- Set up organization for District Portals and LMS
- Set up organization with other Identity providers
- SSO common questions and troubleshooting
- Manage your organization setup
- Manage users
- Overview
- Administrative roles
- User management strategies
- Assign licenses to a Teams user
- In-app user management for teams
- Add users with matching email domains
- Change user's identity type
- Manage user groups
- Manage directory users
- Manage developers
- Migrate existing users to the Adobe Admin Console
- Migrate user management to the Adobe Admin Console
- Overview
- Manage products and entitlements
- Manage products and product profiles
- Manage products
- Buy products and licenses
- Manage product profiles for enterprise users
- Manage automatic assignment rules
- Entitle users to train Firefly custom models
- Review product requests
- Manage self-service policies
- Manage app integrations
- Manage product permissions in the Admin Console
- Enable/disable services for a product profile
- Single App | Creative Cloud for enterprise
- Optional services
- Manage Shared Device licenses
- Manage products and product profiles
- Get started with Global Admin Console
- Adopt global administration
- Select your organization
- Manage organization hierarchy
- Manage product profiles
- Manage administrators
- Manage user groups
- Update organization policies
- Manage policy templates
- Allocate products to child organizations
- Execute pending jobs
- Explore insights
- Export or import organization structure
- Manage storage and assets
- Storage
- Asset migration
- Reclaim assets from a user
- Student asset migration | EDU only
- Manage services
- Adobe Stock
- Custom fonts
- Adobe Asset Link
- Adobe Acrobat Sign
- Creative Cloud for enterprise - free membership
- Deploy apps and updates
- Overview
- Create packages
- Customize packages
- Deploy Packages
- Manage updates
- Adobe Update Server Setup Tool (AUSST)
- Adobe Remote Update Manager (RUM)
- Troubleshoot
- Manage your Teams account
- Renewals
- Manage contracts
- Reports & logs
- Get help
Facing one of these issues? Click the issue for a resolution.
Why add users to Adobe Admin Console
|
As an admin on the Adobe Admin Console, after you've chosen your identity type and set up identity, your next task is to add users to the Admin Console. |
Adobe enterprise and teams, broadly defines two types of users:
Administrators (admins)
Enterprise or teams admins perform administrative tasks on the Admin Console. So, you add admins to define a flexible administrative hierarchy that enables fine-grained management of Adobe product access, and usage, and other administrative tasks.
All admins must be added to the Admin Console. When adding them, the administrative privileges are based on their administrative roles.
End users
End users are the users in your organization or institution who use the Adobe products and services that your organization or institution has obtained as part of the agreement with Adobe.
Depending on your requirements, you add, remove, or update users individually or you can use one of the available bulk upload methods. Use the following matrix as a guide to plan your user management.
If you're a new Adobe enterprise or teams customer, we recommend that you go through this table before you start managing your users on the Admin Console. Existing customers can use this, especially, if they're planning to migrate from one identity type to another (see Edit identity type). |
Individually (Admin Console) |
CSV Bulk upload (Admin Console) | Azure / Google connectors | User Sync Tool | User Management REST API | |
---|---|---|---|---|---|
Applies to | Adobe teams and enterprise customers | Adobe enterprise customers |
|||
Manage users individually in the Admin Console. |
Manage users with CSV file upload in the Admin Console.
|
Manage users (and groups) based on your existing Azure AD portal or Google federation | Manage users (and groups) based on your organization's LDAP. |
||
Add users | Users tab in Admin Console. Read more. |
Use Add users by CSV in Admin Console. Read more. (Use default CSV template.) |
Add users in Azure or Google. Or via Admin Console. |
Users should be added in your organization's LDAP. |
|
Remove users | Select and remove user in Admin Console. Read more |
Choose (Use default CSV template.) |
Users must be removed in Azure or Google. |
Ensure that user information is in sync. Caution: Users not in your organization's LDAP are removed from Admin Console.
|
|
Edit user details | Select the user and then Edit User Details in Admin Console. Read more. |
Choose Edit user details by CSV in the Users tab of Admin Console. Read more. (Use default CSV template.) |
All user information must be changed in Azure or Google. | Ensure that user information is in sync. |
|
Supported Identity types | All | Federated ID |
Federated ID and Enterprise ID | ||
Max. updates per operation | 10 | 25,000 (5,000 for optimal performance) |
Unlimited (Maps to your organization's LDAP) |
Unlimited (Maps to your organization's LDAP) |
|
Requires | Adobe Admin Console | Creating and updating .csv file formats, preferably using Microsoft Excel | You must set up Azure AD or Google federation |
|
Working knowledge of a programming language (such as Python) to consume REST APIs |
Read more | About UMAPI |
Next steps
Create packages
Once added, your users are ready to be assigned with their designated apps and services.
Assign licenses to end users based on your licensing method:
Named User Licensing: Add these users to products (for teams) or product profiles (for enterprises) to give them Adobe product and service entitlements. For more details, see how to create Named User Licensing packages and product profiles.
Shared Device Licensing: Added users can use the configured shared devices which are accessible by Organization users only. For more details, see Create SDL Packages.
Deploy packages
After you've created your package, you must deploy this package to your client machines using one of these methods:
- Go to the client machine and double-click the package file for Windows or macOS.
- Use the Windows command prompt or macOS terminal.
- Use third-party tools: