Using SSO login/sign in

cieTrade allows users with existing Microsoft accounts to authenticate and sign into their cieTrade accounts via SSO log in. SSO through Microsoft Entra allows users to securely access cieTrade using the same Microsoft credentials they already use every day. This simplifies the login experience, reduces password fatigue, and helps improve security by leveraging your organization’s existing Microsoft authentication policies, including multi-factor authentication and account management controls. Once configured, users can move seamlessly into cieTrade without needing to manage a separate username or password.

NOTE: enabling this feature is for the entire database, for all users. However, each user will need to authenticate their own login. If a particular user does not authenticate, they will see the below options, but can use the cieTrade login option instead. 

To set up:

1. Login with the credentials support sent to you or that you received in your welcome email. Then navigate to  Settings> Integrations> click Enable for Microsoft Entra SSO

2. To change your email to the Microsoft email address, go to SettingsUsers & Roles> click on your user and change the Login ID used there. The email in the top of the user profile will be the email you use for emailing out of cieTrade and the login ID email will be your SSO email. 

3. Log out of cieTrade. On the sign in page,  select SSO login instead of cieTrade login. You will be taken to a login page to enter your Microsoft username and password credentials. 3. The next time you login to cieTrade, just click SSO login, you will go straight into the software without needing to be authenticated. Click Accept


NOTE: if you were an existing cieTrade client and want to update your email to use this, please go to Settings> Users & Roles> click on your user and change the Login ID used there. 


If you have additional questions, please contact the Support Team via email to support@cietrade.net.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.