Common Login Issues and How to Fix Them?
Our system supports electronic signatures as part of workflow steps. When a signature is required, users must authenticate by entering their username and password. This article explains how usernames work, highlights common friction points, and provides clear guidance on how to resolve signature login issues.
How Electronic Signature Authentication Works?
To sign electronically, users must enter the same credentials used to log in to Salesforce.
Accepted Username Formats
Your username can be one of the following:
- Alias – usually configured as your first name
- Nickname – usually configured as your last name
- Salesforce Username – usually your email address
Example configuration (recommended):
- Alias: John
- Nickname: Doe
- Username: [email protected]
There are no restrictions on characters or digits:
- All characters and numbers are allowed
Common Friction Points
Users most often experience issues due to one of the reasons below:
1. Password Manager Interference
If you are using a password manager (for example, Google Password Manager), it may automatically fill the username and password fields.
How to identify this issue:
- The username and password fields appear with a blue background
In these cases, the stored credentials may not match what is required for electronic signing.
2. Wrong Environment (Production vs Sandbox)
Electronic signatures are environment-specific, even when the same email address is used.
Common mistakes include:
- Attempting to sign in while connected to the wrong Salesforce org
- Being logged into Sandbox while the signing action requires Production, or vice versa
Important:
Even if your email is the same (for example [email protected]) in both environments, Production and Sandbox are completely separate systems with different credentials.
3. Incorrect Username
Users may enter:
- The wrong identifier (e.g., nickname is not your last name)
- A username that does not exist in the current org
- A username copied from a different environment
4. Attempting to Use SSO Credentials
Electronic signatures do not support SSO-based authentication.
If you normally log in using Single Sign-On, you must still use your Salesforce username and password for signing.
How to Resolve Signature Login Issues?
Follow these steps in order:
1. Enter Credentials Manually
- Manually type your Salesforce username and password
- Do not use auto-filled values from a password manager
This avoids hidden mismatches caused by saved credentials.
2. Verify You Are in the Correct Environment
- Confirm whether the workflow is running in Production or Sandbox
- Make sure you are logged into the same environment where the record exists
3. Confirm Your Username Format
If unsure, try:
- Your Salesforce username (the same user name from log in to the system)
- Your alias
- Your nickname
4. Request a Password Reset
If the issue persists:
- Contact your local system administrator
- Request a Salesforce password reset
Need Further Assistance?
If you continue to experience issues after following the steps above, please reach out to Simploud Success.