Prepare to onboard your organization to the Adobe Admin Console

Because Adobe Workfront is an Adobe product, you can access it through the Adobe Admin Console. This enables you to manage Workfront along with other Adobe accounts and products for your users in a central place.

All Workfront customers will eventually be moved to the Adobe Admin Console. After your organization moves to the Adobe Admin Console, Workfront authentication is managed by the Console. Preparing and making this move sooner lays the groundwork for efficiency in work management and positions your organization for faster innovation in the future

For an overview of the Adobe Admin Console, see Admin Console Overview.

Migration checklist

To ensure that your organization can migrate to the Adobe Admin Console, you must perform the following actions.

  1. Identify the desired Adobe Admin Console where you would like to add Workfront.

    • If your organization does not have an existing Adobe Admin Console, or if you do not want to use an existing Adobe Admin Console, Workfront Support can assist you in creating a new one.

    • If you have multiple Adobe Admin Consoles and you are unsure which one is most appropriate to add Workfront to, contact Workfront Support.

  2. Confirm with Workfront Support that you want to use an existing Adobe Admin Console, or have a new one created.

  3. Set up identity management on the Adobe Admin Console.

    note important
    Be prepared to speak with Workfront Support and your IT team regarding authentication preferences such as Single Sign-on (SSO) or non-SSO.

    For instructions, see the Identity Management section of the Deployment Guide for the Adobe Admin Console.

  4. (Conditional) If using Single Sign-on, connect the new Adobe Admin Console to your existing SSO provider.

    For more information and instructions, see Set up identity.

    note note
    If your organization does not use Single Sign-on, any users migrated to the Adobe Admin Console will receive an email to create their account and password.
  5. Ensure that user email addresses are ready for migration:

    1. Remove duplicate emails from Workfront.

      For instructions, see Update email addresses of existing users in your Workfront instance in Prevent duplicate users.

      If there are duplicate email address in your organization, the user represented by the email address with the most recent lastLoginDate will be moved to the Adobe Admin Console organization. Any other users with that email address will be deactivated.

      note note
      Because only one user with a given email address can be active at a given time, if you need to activate another user with the same email address as a currently active user, you must first deactivate the currently active user before activating the deactivated user.
    2. (Conditional) If you are utilizing custom API integrations, confirm those users have a valid email address that they can access.

    3. (Optional) We recommend deactivating any users who no longer need access to Workfront, so they are not added to the Adobe Admin Console.

    note important
    These actions regarding user emails must be complete before your organization begins moving to the Adobe Admin Console.
  6. (Optional) Update all custom integrations to use OAuth2.

    For instructions on setting up OAuth2 integrations, see Create OAuth2 applications for Workfront integrations.

    note note
    This step is optional, but highly recommended, because other forms of API authentication and authorization will be deprecated in the future.

After your Adobe Admin Console is configured with Workfront, you can use it to create your Workfront system administrators.

For more information, see Manage system administrators in the Adobe Admin Console.

For a list of other actions that are different based on whether your organization has been onboarded to the Adobe Admin Console, see Platform-based administration differences (Adobe Workfront/Adobe Business Platform).