In Salesforce, each user is identified with a username, password, and profile. Together
with other settings, the profile determines which tasks a user can perform, what data the user
can see, and what the user can do with the data.
Unless otherwise specified, users must not share their passwords with other users. Reassign
user credentials to new users only after the previous user is permanently deactivated and no
longer has access to the org’s services and content. If you reuse user credentials as
permitted and described here, reassign only the username. Don’t reassign the password.
Usernames must be unique across all production orgs or all sandboxes, depending on the
instance type. Because Salesforce validates uniqueness for production and sandbox instance
types separately, the same username can exist in both instance types. However, to ensure
that users don’t confuse production and sandbox orgs, we recommend that they create a
separate username for each.
The username must be in the format of an email address, for example, jane@salesforce.com.
The email used in your username need not function or match the email address used for the
account. You can have the same email address associated with your account across multiple
orgs. For example, create unique usernames like jane@company.sandbox and
jane@trialorg.company.com, for different accounts that are associated with the same email
address. Keep in mind that Salesforce Customer Support can’t change usernames or deactivate
users from an org. If you get a Duplicate Username error, check if the username is already
in use in your production, trial, or Sandbox orgs. Deactivate or change the username for the
user record, then create your account with your desired username in your production org. If
you’re unable to change or deactivate a username, contact your Salesforce admin for help. If
you’re unable to locate the org where the username is already in use, try a different
username to create your account.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.