Embedded Files
BREAKING NEWS 8/1
What is a Single Sign-On (SSO) Account?
What is a Single Sign-On (SSO) Account?
A Single Sign-On (SSO) is a combination of multiple Tax ID Numbers or Provider IDs that can have one login to the Zelis Provider Portal. A user can log in to the “primary” account for the Single Sign On (SSO) and view all the other accounts associated with the Single Sign-On (SSO) Account.
How Do I Handle an SSO Request?
How Do I Handle an SSO Request?
Once you speak with an authorized decision-maker, you will ask which Tax ID Number they want to become the primary account. The primary TIN will be the only TIN the caller can change information on. In addition, you must verbally verify that the caller is the ADM for each secondary TIN along with making sure the other TIN's are enrolled in a product (not 835). You will only need to conduct a 2-Step verification for the primary TIN regardless of how many other TID numbers the caller provides for the request.
Steps After Completing 2-Step Verification?
Steps After Completing 2-Step Verification?
After you complete the 2 Step Verification, you will submit the SSO template to a member of management. Management will then forward the submission appropriately. Inform the caller it they will then review and build the Single Sign On (SSO) for the accounts requested, and this can take 3-5 business days to complete.
Things to know about a Single Sign On
Things to know about a Single Sign On
All accounts requested must be enrolled in a Zelis Payment Product (835 Only Excluded).
All users must be logged into the portal under the primary account associated with the Single Sign On (SSO), and the user must have the permission “Access to Subordinates” checked in order to view all accounts associated with the Single Sign On (SSO).
The Administrator for the primary account is in charge of all other users’ permissions and granting them access to the other accounts.
When the user is viewing the secondary accounts, it is “Read Only” as they can only view and download the payment data if deemed appropriate by the Administrator. No changes can be made to a secondary TIN account while logged in under the primary account.
SSO Template
SSO Template
All information must be filled out
Practice/Provider:
Product Enrolled:
Caller Full Name:
Caller Title:
Caller Phone:
Caller Email:
Is caller admin or is there an admin update request placed for caller? (If no, request cannot be completed): Y/N
2 Step Completed on Primary TIN (If no, request cannot be completed): Y/N
Authorized Decision Maker on Secondary TIN(s)? (If no, request cannot be completed): Y/N
Primary TIN:
Primary Provider ID:
Secondary TIN(s):
Secondary Provider ID(s):
Is there an existing SSO for any of the TINs/Provider IDs listed above?
If yes, is the requester aware of this?
If yes, does the requester wish to remove the TIN(s) from the existing SSO and place it/them under the new SSO?
If yes, does this requester have the authority to do so?
Page updated
Google Sites
Report abuse