There can be multiple scenarios that may cause you trouble logging into your Freshservice instance. Here are some recommendations to troubleshoot the issue.


  1. Check for deactivated user
  2. Try logging in after password reset.
  3. Check for primary email for SSO login.
  4. Check for common browser issues.


Check for deactivated user

When your account is either deactivated or unused for a long time, contact your Admin to reactivate your account. As an Administrator of your servicedesk, follow the steps below to check and reactivate users.

  1. Navigate to Admin. Under the User Management section, select Agent or Requester.

  2. Click on the Deactivated tab and check for the user profile facing the login issue.

  3. Select the deactivated user profile and click on the Reactivate button.

  4. This will take you to the Edit agent/requester page where you can update the roles and permissions of the user.

  5. Once done, click on Update to reactivate the user.


    Reactivating a deactivated user


Try logging in after password reset.

If you're having trouble logging in using the Freshworks login, 

  1. Click on the 'Forgot your password' to reset your password from your login page. 

  2. Select the ‘Request reset link’ option.

  3. Reset the password using the link from the password reset email.

  4. Try to log in again with the new password and check if the issue persists.


    Resetting your password



Check for primary email for SSO login.

Check if you're using the secondary email address to log in through SSO. Please note that you can only use the primary email address for SSO login.

As an Administrator of your Freshservice account, you can check if a requester is using their secondary email to login by following the steps below.

  1. Navigate to Admin. Under the User Management section, select the Requester option.

  2. Click on the requester profile facing login issues, and choose the Edit Requester option under the More dropdown. 

  3. Scroll down and check for the email addresses provided under the Secondary emails section.

  4. Emails mentioned under secondary emails should not be used to login through SSO.

    Checking for Secondary email address of a requester.

You can also access your Freshservice instance when your SSO server is down.

Check for common browser issues.

Clear cache and cookies on your web browser and try to sign in again. You can also open an incognito window to access your Freshservice instance to eliminate any extensions that limit your access.

If you still need help logging in after working through all of the above recommendations, please reach out to support@freshservice.com.