Skip to main content
Migrate to the Thomson Reuters Account for ONESOURCE customers
Search
Search Account management Support Help and Support.

This article applies to:

  • Product: ONESOURCE Platform

Common questions

Can migrated users still use Universal ID?

  • No. Once your profile is upgraded to the Thomson Reuters Account in a specific customer account, Universal ID can no longer be used for sign-in in that customer account.
  • If you also have profiles in other tenants that haven’t yet been upgraded, you will still use Universal ID and password for those until those customer accounts are migrated.
  • Example:
    • Tenant A (migrated): Use email and Thomson Reuters Account password or SSO.
    • Tenant B (not migrated): Continue using Universal ID and password.

Why is the password field visible for some users but hidden for others on the
Administration User Details
 page?

  • If the sign-in method is Universal ID (legacy): The administrator must set a password when creating or editing the user. The user signs in using that Universal ID and password.
  • If the sign-in method is Thomson Reuters Account (new): The password field is hidden because the password is managed directly by Thomson Reuters Account. Instead, the user receives an email to set or reset their own Thomson Reuters Account password.
  • Difference between the 2 sign in methods:
Aspect
Universal ID sign-in (Legacy)
Thomson Reuters Account sign-in (New)
Username
Universal ID (assigned in ONESOURCE)
Email address (verified with Thomson Reuters Account)
Password
Set manually by the administrator on the User Details page
Managed by Thomson Reuters Account (user receives email to set/reset password)
Sign-in Method Selection
Administrator selects Universal ID as sign-in method
Administrator selects Thomson Reuters Account as sign-in method
Sign-in Screen
ONESOURCE legacy sign-in page
Thomson Reuters Account sign-in page
Authentication Options
Username and password only
Email and Thomson Reuters password OR Enterprise SSO (if configured)
Profile Selection
Not available
Available: users select from multiple profiles tied to their email
User Creation
Password required during user creation
Password field hidden; Thomson Reuters Account manages credentials
Future Support
Being phased out
Long-term supported method

I have multiple user profiles within a single tenant, and all are associated with the same email. Will all these profiles upgrade simultaneously?

Yes. When you initiate the upgrade for 1 user profile in the signed in customer account, then all other users associated to the same email will upgrade together. You only need to complete the registration (verify email and set password) once for that tenant.

If I upgrade in 1 customer account, will the users in other customer account also upgrade?

No. Migration is handled by customer to customer bases.
If you have access to multiple customer accounts with the same email:
  • Each account administrator must flag you separately and you must complete the upgrade process in each customer account.
  • The
    Choose Your Profile
     page will show only those user profiles that have been migrated to Thomson Reuters Account.
  • User profiles in accounts that are not yet migrated will appear grayed out or hidden, with guidance to continue using Universal ID and ONESOURCE password (legacy sign-in) for those users.
The benefit is that once you’ve set up your Thomson Reuters Account password, you won’t need to re-register; you’ll sign in and confirm the upgrade for other customer accounts.
The Universal ID sign-in can only be used for accounts where you haven’t been upgraded yet.
Customer Account
Details
Customer Account A
The user is upgraded: Use the Thomson Reuters Account sign-in method.
Customer Account B
The user is not upgraded: Use ONESOURCE legacy sign-in method.

Is Bypass SSO still supported?

Yes. ONESOURCE tenants that use SSO can still exempt certain users (for example, external contractors, auditors).
Administrators manage these exemptions in
Administration
Setup
SSO Exemptions
.
Exempted users must use the special Bypass URL. If they use the standard sign-in page, they’ll be redirected through the SSO workflow.
On the Bypass page, exempted users will sign in with their email and Thomson Reuters Account password instead of going through their company’s SSO.

Why can't a newly created user sign in with Universal ID and password?

This happens if the administrator chose
Thomson Reuters Account
 as the sign-in method at the time of user creation.
In that case, the user must sign in with their email and Thomson Reuters Account password (or via SSO).
The Universal ID is still stored in the backend for internal tracking, but it can't be used for sign-in once the Thomson Reuters Account is selected.

Why is the sign-in method locked to Thomson Reuters ID when creating a user?

In customer accounts where Thomson Reuters Account is enabled and the
Create users in Thomson Reuters Account
 setting is turned on under
Administration
Setup
Thomson Reuters Upgrade
 page; new users are required to use Thomson Reuters Account. The sign-in method is therefore fixed and enforced to Thomson Reuters ID by design.

How are
Account Linking
 and
Account Mapping
 changing with Thomson Reuters Account?

Overview of
Account Linking
 and
Account Mapping
 in the previous state (in ONESOURCE) versus the new state (Thomson Reuters Account):
Current ONESOURCE Methods (prior to migration):
  • Account Linking
    : Users sign in using their ONESOURCE Universal ID and password once. After that, the account is linked to their corporate sign-in via the SSO.
  • Account Mapping
    : The corporate network sign-in is automatically mapped to the ONESOURCE Universal ID using a unique identifier such as Employee ID, Network ID, or Email. Users are logged in directly via SSO without seeing the ONESOURCE sign-in screen.
With Thomson Reuters Account:
  • Both
    Account Linking
     and
    Account Mapping
     are consolidated into a single, simplified method.
    • Email-based mapping replaces previous methods entirely. Thomson Reuters Account uses email as the universal identifier for authentication across all Thomson Reuters products.
    • When a user signs in using an email from a reserved domain, Thomson Reuters Account automatically routes them through the appropriate enterprise SSO connection, associating their user identity based on that email.
important
Customers accustomed to previous terms (Linking and Mapping) should now consider these combined into 1 unified, email-based approach in Thomson Reuters Account.

What do firms need to do to prepare for this new email-based mapping model?

Firms must work with their Identity Provider (IdP) to ensure their SSO setup:
  • Passes the correct email address to the Thomson Reuters Account during sign-in.
  • Uses email as the primary unique identifier instead of Employee ID or Network ID.
If needed, firms should involve their Professional Services team and SSO team to:
  • Reserve their domain in Thomson Reuters settings.
  • Set up or update their SSO connection accordingly.
  • Verify that email attributes are correctly mapped in their IdP configurations.