Prepare to onboard your organization to the ÃÛ¶¹ÊÓƵ Admin Console
Because ÃÛ¶¹ÊÓƵ Workfront is an ÃÛ¶¹ÊÓƵ product, you can access it through the ÃÛ¶¹ÊÓƵ Admin Console. This enables you to manage Workfront along with other ÃÛ¶¹ÊÓƵ accounts and products for your users in a central place.
All Workfront customers will eventually be moved to the ÃÛ¶¹ÊÓƵ Admin Console. After your organization moves to the ÃÛ¶¹ÊÓƵ 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 ÃÛ¶¹ÊÓƵ Admin Console, see .
Migration checklist
To ensure that your organization can migrate to the ÃÛ¶¹ÊÓƵ Admin Console, you must perform the following actions.
-
Identify the desired ÃÛ¶¹ÊÓƵ Admin Console where you would like to add Workfront.
-
If your organization does not have an existing ÃÛ¶¹ÊÓƵ Admin Console, or if you do not want to use an existing ÃÛ¶¹ÊÓƵ Admin Console, Workfront Support can assist you in creating a new one.
-
If you have multiple ÃÛ¶¹ÊÓƵ Admin Consoles and you are unsure which one is most appropriate to add Workfront to, contact Workfront Support.
-
-
Confirm with Workfront Support that you want to use an existing ÃÛ¶¹ÊÓƵ Admin Console, or have a new one created.
-
Set up identity management on the ÃÛ¶¹ÊÓƵ Admin Console.
note important 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 .
-
(Conditional) If using Single Sign-on, connect the new ÃÛ¶¹ÊÓƵ Admin Console to your existing SSO provider.
For more information and instructions, see .
note note NOTE If your organization does not use Single Sign-on, any users migrated to the ÃÛ¶¹ÊÓƵ Admin Console will receive an email to create their account and password. -
Ensure that user email addresses are ready for migration:
-
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
lastLoginDatewill be moved to the ÃÛ¶¹ÊÓƵ Admin Console organization. Any other users with that email address will be deactivated.note 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. -
(Conditional) If you are utilizing custom API integrations, confirm those users have a valid email address that they can access.
-
(Optional) We recommend deactivating any users who no longer need access to Workfront, so they are not added to the ÃÛ¶¹ÊÓƵ Admin Console.
note important IMPORTANT These actions regarding user emails must be complete before your organization begins moving to the ÃÛ¶¹ÊÓƵ Admin Console. -
-
(Optional) Update all custom integrations to use OAuth2.
For instructions on setting up OAuth2 integrations, see Create OAuth2 applications for Workfront integrations.
note 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 ÃÛ¶¹ÊÓƵ Admin Console is configured with Workfront, you can use it to create your Workfront system administrators.
For more information, see Manage users in the ÃÛ¶¹ÊÓƵ Admin Console.
For a list of other actions that are different based on whether your organization has been onboarded to the ÃÛ¶¹ÊÓƵ Admin Console, see Platform-based administration differences (ÃÛ¶¹ÊÓƵ Workfront/ÃÛ¶¹ÊÓƵ Business Platform).