It is a shared experience among Salesforce administrators and non-admins to encounter login issues due to the high level of security of the CRM platform. Your Salesforce org is the repository of all the invaluable data your org needs to function fully. Hence, it deserves to be protected efficiently. Salesforce has several security measures in place to protect your org. This article will delve into some common issues and guide you on resolving them, making your troubleshooting efforts more manageable.
Troubleshooting in Salesforce involves identifying the root cause of technical problems. These issues may stem from various areas such as sharing settings, reports, dashboards, and org access. This article will primarily address login issues. To clarify, here are some login issues that both administrators and non-administrators may encounter when using Salesforce:
A user can encounter flexibility issues logging into the org if their profile is not attached to a trusted IP range in Salesforce. IP address ranges in Salesforce primarily allow users to specify a set of IP addresses where logins are allowed. This can be set from the profile level or by searching “Network Access” in the Quick Find box in the Setup interface. This security feature ensures that the admin controls the level of access that specific profiles have to log into the company's internal network. Users can log in at stated IP addresses more flexibly with the IP address range feature.
The image above demonstrates how to access and set the Trusted IP Ranges feature in Salesforce.
Have you ever gotten a pop-up note that reads, “Please check your username and password. If you still can't log in, contact your Salesforce administrator.” while trying to log in to your Salesforce account? Well, a user encounters log-in problems if their credentials are incorrect. With an incorrect username or password, they are refused access to the org and might have to contact this admin to resolve such issues.
The image above shows a user attempting to log into a Salesforce org with an incorrect password.
Login Hours in Salesforce stipulate when users can log in based on the time configurations on their profiles and settings. If a user attempts to log into the org outside the stipulated login hours set for their profile, they will encounter a snag. Again, this can also be resolved.
The image above shows how to set Login Hours in Salesforce via profiles.
Remember, the essence of this article is not just to show you what problems exist when trying to log into a Salesforce org but also to show a user, admin or non-admin, how to troubleshoot them.
If you cannot log into your Salesforce org, you can reset your password by clicking “Forgot Your Password.” The user will be asked to enter their username, and an email with instructions will be sent to reset their password. This should first be considered before contacting the System Administrator. Contact your organization’s System Administrator for a password reset if you:
The above image illustrates the process of resetting your password as a non-admin user by clicking the “Forgot Your Password” link in Salesforce.
Several troubleshooting methods are available when dealing with incorrect usernames and passwords on Salesforce. It is important to remember that Salesforce passwords are case-sensitive and must be at least eight characters long. If you encounter login issues, double-check that your Password is entered in the correct case.
While your username does not have to be the exact email you registered with, it must be in an email format. It is recommended that users manually type in their passwords instead of relying on saved Passwords. If these steps do not work for non-admin users, they should contact their system administrator. The Salesforce administrator can then change the users’ passwords by navigating to Setup >> Users >> Select the user >> Change Password.
The above image demonstrates that Salesforce Administrators can change users' passwords from the user's detail section.
System administrators must check the login history of their org\ to fully comprehend the error each user faces when logging in. If, in the login history, a user has a login error that reads “Failed: Computer activation required entry,” the System Administrator is advised to check the Identity Verification History page under Setup and verify where Salesforce is trying to send the user’s verification code. The user could be checking in the wrong place. The Identity Verification History page shows the time, username, error gotten, and location of the user can be tracked. If the user does not receive their code in their email, troubleshoot by checking their spam or hidden folders.
The above image displays the Identity Verification History page in Salesforce.
In this article, we have explored various login issues that users may encounter when attempting to access an org. While this list isn't exhaustive, it addresses common login issues most users experience and recommends the best troubleshooting methods.
