Adobe-supported identity types

Adobe’s identity management system helps admins create and manage user access to applications and services. Adobe offers three varying types of identities or accounts to authenticate and authorize users. They use an email address as the user name. These identity types are:

  • Federated ID: Created, owned, and managed by an organization and linked to the enterprise directory via federation. The organization manages credentials and processes Single Sign-On via a SAML2 Identity Provider (IdP).
  • Enterprise ID: Created, owned, and managed by an organization. Adobe hosts the Enterprise ID and performs authentication, but the organization maintains the Enterprise ID.
  • Adobe ID: Created, owned, and managed by the end user. Adobe performs the authentication, and the end user manages the identity.

Based on your organizational needs, you can select the most appropriate identity model to implement and use. See the table below to learn more about them.

Components Features Adobe ID Enterprise ID Federated ID

Account ownership and control

The organization creates, owns, and manages the account.

Maintain control of entitlements and the stored user-generated content on behalf of the user.

Data ownership and control

The organization owns the data, files, and assets associated with the account.

End the users’ access to company-owned assets on de-provisioning.

Uses content logs to help admins view how users are interacting with company-owned assets.

Limits asset sharing.

Enterprise features

Helps the organization leverage storage.

Supports multi-factor authentication.

To learn how to set up Enterprise and Federated IDs, see Set up identity.

Choosing the correct identity model can have a considerable impact on the way an organization stores and shares assets. The Enterprise and Federated ID models are an ideal choice for enterprises, while Adobe ID is best suited for individuals. In addition to containing all features of Adobe ID, they also support the best data practices and ensure effective software deployment.

As seen already, there are some obvious advantages that Enterprise and Federated IDs have over Adobe ID:

  • By offering strict administrative controls, they ensure an effective monitoring of products and services.
  • Users lose access to organizational files, data, and assets after their affiliation ends with the organization.
  • Federated ID provides multi-factor authentication and is the most secure identity model out of all three.

Adobe ID works best when there is no need for internal control. It is user-friendly, but not the best option to use the enterprise storage. As your end users may not always adhere to the best practices, it is advisable to use Federated and Enterprise IDs. However if you are still uncertain which identity model is right for you, contact Adobe Customer Care.


There are some products and services such as Adobe Licensing Website and Adobe Forums that only support Adobe ID.

Edit Identity Type

As a System Administrator, you can change the identity type for users in your organization. Edit the following identity types of users through the Admin Console:

  • Adobe ID to Enterprise ID,
  • Adobe ID to Federated ID,
  • Enterprise ID to Federated ID, or
  • Federated ID to Enterprise ID.

You need a new or an existing directory to change the identity type of a user from Enterprise ID to Federated ID or vice versa. For more details, see move domains across directories.

To know more about user identity types, see Adobe-supported identity types.

Impact on Creative Cloud end users

If you edit the identity type of users from Adobe ID to Federated/Enterprise ID, these users continue to have access to their personally owned Adobe ID. However, they access the organization’s Adobe apps, services, and solutions through the new Federated ID or Enterprise ID assigned to them.

If your users already have Adobe IDs with assets linked to it, they can migrate assets from their Adobe ID accounts to their new enterprise account.

If existing Creative Cloud users were using services that are not included with Creative Cloud for enterprise, their memberships revert to free versions.

Edit Identity Type by CSV

The following procedure enables you to edit the identity type for users in bulk. You can also edit user details such as email addresses and names for users using the Admin Console, User Sync tool, or the User Management API.

  1. Sign in to the Admin Console and navigate to Users.

  2. Click , and select Edit Identity Type by CSV from the drop-down list.

    The Edit Identity Type by CSV dialog box displays.

    Edit Identity Type by CSV
  3. To include users to edit Identity type, download the Current User List or the CSV Standard Template, clicking Download CSV Template.

    The .csv file downloaded, contains the following data.

    • Identity Type - Federated ID, Enterprise ID, or Adobe ID
    • Username
    • Domain
    • New Identity Type - Federated ID, Enterprise ID, or Adobe ID
    • New Email
    • New Username
    • New Country Code
  4. Open the .csv file in an application capable of editing CSVs and edit the identity types, as required.


    When you are editing the identity type from Adobe ID to Federated/Enterprise ID, the email address for Adobe ID must match the one for enterprise account.

  5. Open the Edit Identity Type by CSV dialog box, and upload the updated .csv file. Ensure that this file is saved with UTF-8 encoding.

    Once the process is complete, you receive a notification email.

This process migrates the permissions and provisioned products for all migrated users. The users whose identity has changed, receive a notification to use their new Enterprise/Federated ID account when working with the Adobe products they have been provisioned.

In addition, if your users were previously using Adobe IDs and have assets linked to it, these users will be requested to consent to the Asset Migration process. The Asset Migration process automatically moves the users' assets from their Adobe ID account to their Enterprise account.

Asset migration

When you edit the identity type of the users from Adobe ID to Federated ID/Enterprise ID, users can migrate the supported content from their existing company assigned Adobe ID account to their new enterprise account. The migration can be done in two ways:

For users to automatically migrate their content, they must be assigned access to storage/services for both, Creative Cloud and Document Cloud. For users to have access to storage for Creative Cloud and Document Cloud, do one of the following:

  • Assign a Product Profile which offers the Creative Cloud All Apps plan with storage, and has the PDF Services turned On.
  • Assign a Creative Cloud Product Profile with storage, and a Document Cloud Product Profile with storage (excludes desktop only offers) and PDF Services turned On.


All product licenses that the user is assigned to, must have storage included. Otherwise, Asset Migration fails. For example, an Adobe ID user allocated to a single app license for Photoshop with no storage and another single app license for XD with 100-GB storage cannot migrate the assets automatically.

After the Edit Identity Type process is complete, the end user receives an email notification with the details to migrate their assets.

As the IT Admin, you can download the Asset Migration completion status report for all the users that were part of the Edit Identity process. To download the report, do the following:

  1. Navigate to Admin Console > Users.

  2. Click  and select Export migration report to CSV from the drop-down list.

    The report is downloaded.

This report tells you who has granted consent, who has denied consent, and who hasn’t taken any action yet. To know about the type of content that the migration process supports, see Asset Migration FAQ.


Sometimes, the automatic Asset Migration process cannot be triggered for a few users. These users receive a notification to transfer their content manually, and are excluded from the migration report.

Join the conversation


If you have any questions or observations around the topics, concepts, or procedures described in this article, join the discussion.

Join Now

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy