|
Accessibility Mode
|
When selected, enables a user interface mode designed for visually impaired
users. |
|
Active
|
Administrative checkbox that enables or disables user login to the
service. |
|
Address
|
Street address for user. Up to 255 characters are allowed in this
field. |
|
Alias
|
Short name to identify the user on list pages, reports, and other pages where
the entire name doesn’t fit. Up to 8 characters are allowed in this field. |
|
Allow Forecasting
|
Indicates whether the user can use forecasts. |
|
Api Token
|
Indicates whether an API token has been reset. If issues occur, Salesforce uses
this field to help you troubleshoot issues related to API tokens. |
|
App Registration: One-Time Password Authenticator
|
When connected, the user can verify their identity with a code from a
third-party authenticator app, such as Google Authenticator, Microsoft
Authenticator, or Authy. For example, the user enters a code from the app when
logging in from an IP address outside the company’s trusted IP range. This type of
verification code is sometimes called a time-based one-time password, or
TOTP.
Users with Multi-Factor Authentication for User Interface Logins
permission must provide two authentication factors when logging in to Salesforce
through the user interface: their username and password, followed by a separate
verification method. A current verification code generated by an authenticator app
counts as a verification method.
If the user has Multi-Factor Authentication
for API Logins permission and connects an authenticator app, the user enters the
current code from the app to access the service. The user doesn’t enter the
standard security token.
|
|
App Registration: Salesforce Authenticator
|
When connected, the user can verify their identity by responding to a push
notification with the Salesforce Authenticator mobile app, version 2 or later. For
example, the user approves a notification when logging in from an IP address outside
the company’s trusted IP network. If the user sets a trusted location in the app and
is allowed to use location-based automated verifications, Salesforce Authenticator
can automatically verify the user’s identity from that trusted location. Users can
connect both Salesforce Authenticator and another authenticator app to the same
Salesforce account.
When connected, the user can also verify identity with a code
from Salesforce Authenticator. For example, the user enters a code from the app
when logging in from an IP address outside the company’s trusted IP network. This
type of verification code is sometimes called a time-based one-time password, or
TOTP.
Users with Multi-Factor Authentication for User Interface Logins
permission must provide two authentication factors when logging in to Salesforce
through the user interface: their username and password, followed by a separate
verification method. A manual or automated response to a notification from
Salesforce Authenticator counts as a verification method.
If the user has
Multi-Factor Authentication for API Logins permission and connects Salesforce
Authenticator, the user enters the current code from the app to access the
service. The user doesn’t enter the standard security token.
|
|
Call Center
|
The name of the call center to which this user is assigned. |
|
Checkout Enabled
|
Indicates whether the user is notified by email when the user’s Checkout
account is activated and available for login.
Enabling this option requires the
Manage Billing permission.
|
|
City
|
City portion of user’s address. Up to 40 characters are allowed in this
field. |
|
Color-Blind Palette on Charts
|
Indicates whether the option to set an alternate color palette for charts has
been enabled. The alternate palette has been optimized for use by users who want
high-contrast. For dashboard emails, the alternate palette isn’t used. |
|
Company
|
Company name where user works. Up to 40 characters are allowed in this
field. |
|
Contact
|
Name of the associated contact if the user is a partner user. |
|
Country
|
Country portion of user’s address. Entry is selected from a picklist of
standard values, or entered as text. Up to 80 characters are allowed if the field is
a text field. |
|
Created By
|
User who created the user including creation date and time. (Read only) |
|
Currency
|
User’s default currency for quotas, forecasts, and
reports. Shown only in orgs using multiple currencies. This currency must be one
of the active currencies for the org.
|
|
Custom Links
|
Listing of custom links for users as set up by your administrator. |
|
Default Currency ISO Code
|
User’s default currency setting for new
records. Available only for orgs that use multiple currencies.
|
|
Default Division
|
Division that is applied, by default, to all new accounts and leads created by
the user, unless the user explicitly sets a different division. When users create
records related to an account or other record that already has a division, the new
record is assigned to the existing record’s division. The default division isn’t
used.
This setting doesn’t restrict the user from viewing or creating records in
other divisions. Users can change their default division at any time by setting a
working division.
Available only in orgs that use divisions to segment
their data.
|
|
Delegated Approver
|
User lookup field used to select a delegate approver for approval requests.
Depending on the approval process settings, this user can also approve approval
requests for the user. |
|
Department
|
Group that user works for, for example, Customer Support. Up to 80 characters
are allowed in this field. |
|
Development Mode
|
Enables development mode for creating and editing Visualforce pages.
This
field is visible only to orgs that have Visualforce enabled.
|
|
Disable Auto Subscription For Feeds
|
Disables automatic feed subscriptions to records owned by a user. Only
available in orgs with Chatter enabled. |
|
Division
|
Company division to which user belongs for example, PC Sales Group. Up to 40
characters are allowed in this field. |
|
Email
|
Email address of user. Must be a valid email address in the form:
jsmith@acme.com. Up to 128 characters are allowed in this field. |
|
Email Encoding
|
Character set and encoding for outbound email sent by user from within
Salesforce. English-speaking users use ISO-8859-1, which represents all Latin
characters. UTF-8 (Unicode) represents characters for all languages, however some
older email software doesn’t support it. Shift_JIS, EUC-JP, and ISO-2022-JP are
useful for Japanese users. |
|
Employee Number
|
Identifying number for a user. |
|
End of day
|
Time of day that user generally stops working. Used to define the times that
display in the user’s calendar. |
|
Fax
|
Fax number for user. |
|
Federation ID
|
The value used to identify a user for federated authentication single
sign-on. |
|
First Name
|
First name of user, as displayed on the user edit page. Up to 40 characters are
allowed in this field. |
|
Flow User
|
Grants the ability to run flows. Available in Developer (with limitations),
Enterprise, Unlimited, and Performance Editions.
Enabling this option requires the
Manage Flow permission.
If the user has the Run Flows permission, don’t
enable this field.
|
|
Lightning Platform Quick Access Menu
|
Enables the Lightning Platform quick access menu, which appears in object list
view and record detail pages. The menu provides shortcuts to customization features
for apps and objects. |
|
Information Currency
|
The default currency for all currency amount
fields in the user record. Available only for orgs that use multiple
currencies.
|
|
Knowledge User
|
Grants access to Salesforce Knowledge. The user’s profile determines whether
the user has access to the Article Management tab or Articles tab. Available in
Professional, Enterprise, Unlimited, and Performance Editions. |
|
Language
|
The primary language for the user. All text and online
help is displayed in this language. In Professional, Enterprise, Unlimited, and
Performance Edition orgs, a user’s individual Language setting overrides the org’s
Default Language.
Not available in Personal Edition, Contact Manager, or
Group Edition™. The org’s Display Language applies to all users.
|
|
Last Login
|
The date and time when the user last successfully logged in. This value is
updated if 60 seconds have elapsed since the user’s last login. (Read only) |
|
Last Name
|
Last name of user, as displayed on the user edit page. Up to 80 characters are
allowed in this field. |
|
Last Password Change or Reset
|
The date and time of this user’s last password change or reset. This read-only
field appears only for users with the Manage Users permission. |
|
Lightning Login
|
Allows the user to enroll in and use Lightning Login, for password-free logins.
The Enroll option indicates that a Salesforce admin has given the user the option to
enroll. The Cancel option indicates that the user has enrolled, and can cancel their
enrollment if needed. |
|
Locale
|
Country or geographic region in which user is
located.
The Locale setting affects the format of date, date/time,
and number fields, and the calendar. For example, dates in the English (United
States) locale display as 06/30/2000 and as 30/06/2000 in the English (United
Kingdom) locale. Times in the English (United States) locale display using a
twelve-hour clock with AM and PM (for example, 2:00 PM), whereas in the English
(United Kingdom) locale, they’re displayed using a 24-hour clock (for example,
14:00). The user’s Language setting determines the language
of the AM/PM designator in date/time fields. For example, if the user’s language
is English, times in the Chinese (Singapore) locale display with English AM/PM
designators.
The Locale setting also affects the first
and last name order on Name fields for users, leads, and
contacts. For example, Bob Johnson in the English (United States) locale displays
as Bob Johnson, whereas the Chinese (China) locale displays the name as Johnson
Bob.
For Personal Edition users, the locale is set at the org level (from Setup, enter
Company Information in the Quick Find box, then select
Company Information). For all other users, their personal
locale, available at their personal information page, overrides the org
setting.
|
|
Make Setup My Default Landing Page
|
When this option is enabled, users land in the Setup page when they log
in. |
|
Manager
|
Lookup field used to select the user's manager. This field:
- Establishes a hierarchical relationship, preventing you from selecting a user
that directly or indirectly reports to itself.
- Allows Chatter to recommend people and records to follow based on your org's
reporting structure.
This field is especially useful for creating hierarchical workflow rules and
approval processes without creating more hierarchy fields.
Unlike other
hierarchy fields, you can inactivate users referenced in the Manager
field.
|
|
Marketing User
|
When enabled and the user has Read permission on contacts or the Import
permission on Leads, and Edit permission on campaigns, the user can create, edit,
and delete campaigns, configure advanced campaign setup, and add campaign members
and update their statuses with the Data Import Wizard. Available in Professional,
Enterprise, Unlimited, and Performance Editions.
If this option isn’t selected, or
the user doesn’t have the necessary permissions, the user can only view campaigns
and advanced campaign setup, edit the Campaign History for a single lead or
contact, and run campaign reports.
|
|
Middle Name
|
Middle name of the user, as displayed on the user edit page. Up to 40
characters are allowed for this field.
To enable this field, from Setup, enter
User Interface in the Quick Find box, then select
User Interface. In Lightning Experience, the User
Interface page is the last item under the User Interface node. Then select
Enable Middle Names for Person Names.
|
|
Mobile
|
Cellular or mobile phone number. Up to 40 characters are allowed in this field.
This number is used for SMS-based device activation. Administrators enable
SMS-based device activation from Setup by entering Session
Settings in the Quick Find box, then selecting Session
Settings, and then selecting the Enable the SMS method of
device activation option.
After the SMS method of device
activation is enabled, users without a verified mobile number in their profiles
are asked after logging in to register for mobile verification. This process
applies to users without mobile numbers. Users can take one of the following
actions. After a user’s mobile phone number is verified, Salesforce uses it to
authenticate the user when necessary. For example, verification occurs when a user
logs in from an unknown IP address.
- Enter a mobile phone number and then have it verified with a text message
containing a verification code.
- Skip entering a mobile number now, but be asked again at the next login.
- Opt out of mobile verification. Users who select this action can register a
mobile number later in their personal information. Chatter Free and Chatter
External license users who select this action need an administrator to set the
mobile number.
Administrators can also enter users’ mobile numbers and pre-verify them. If
Enable the SMS method of device activation is enabled
when an administrator enters a mobile number for a user, or when a mobile number
is set from an API using the User object, the mobile number is
considered verified. If Enable the SMS method of device
activation isn’t enabled, the new mobile phone number isn’t
considered verified.
|
|
Mobile Configuration
|
The mobile configuration assigned to the user. If no mobile configuration is
specified, this field defaults to the mobile configuration assigned to the user’s
profile.
This field is visible to orgs that use Salesforce to manage mobile
configurations.
|
|
Modified By
|
User who last changed the user fields, including modification date and time.
(Read only) |
|
Monthly Contact and Lead Limit
|
The default number of records per license is 300, but you can assign more or
fewer, up to the org limit. |
|
Name
|
Combined first name, middle name (beta), last name, and suffix (beta) of user,
as displayed on the user detail page. |
|
Nickname
|
A nickname is the name used to identify this user in an Experience Cloud site.
Up to 40 alphanumeric characters are allowed. Standard users can edit this
field. |
|
Offline User
|
Administrative checkbox that grants the user access to Connect Offline.
Available in Professional, Enterprise, Unlimited, and Performance Editions. |
|
Partner Super User
|
Denotes whether a partner portal user is a super user. |
|
Phone
|
Phone number of user. Up to 40 characters are allowed in this field. |
|
Profile
|
Administrative field that specifies the user’s base-level permissions to
perform different functions within the application. You can grant more permissions
to a user through permission sets. |
|
Receive Approval Request Emails
|
Preference for receiving approval request emails.
This preference also
affects whether the user receives approval request notifications in the Salesforce
mobile app or Lightning Experience.
|
|
Receive Salesforce CRM Content Daily Digest
|
Specifies that non-portal users with a Salesforce CRM Content User license and
Salesforce CRM Content subscription receive a daily email summary if activity occurs
on their subscribed content, libraries, tags, or authors. To receive email, you must
also select the Receive Salesforce CRM Content Email Alerts
option. Portal users don’t need the Salesforce CRM
Content User license. They need only the View Content in Portals user
permission. |
|
Receive Salesforce CRM Content Email Alerts
|
Specifies that non-portal users with a Salesforce CRM Content User license and
Salesforce CRM Content subscription receive email notifications if activity occurs
on their subscribed content, libraries, tags, or authors. To receive real-time email
alerts, select this option and don’t select the Receive Salesforce CRM
Content Daily Digest option. Portal users don’t need the Salesforce CRM
Content User license. They need only the View Content in Portals user
permission. |
| Return Address |
The user’s return email address for email sent from Salesforce. |
|
Role
|
Administrative field that specifies position of user within an organization,
for example, Western Region Support Manager. Roles are selected from a picklist of
available roles, which the administrator can change. Users with the View Roles and
Role Hierarchy permission can view role information.
Not available in Personal
Edition, Contact Manager, or Group Edition.
|
|
Salesforce CRM Content User
|
Indicates whether a user can use Salesforce CRM Content. Available in
Professional, Enterprise, Unlimited, and Performance Editions. |
|
Self-Registered via Customer Portal
|
When enabled, specifies that the user was created via self-registration to a
Customer Portal. Available in Enterprise, Unlimited, and Performance
Editions. |
|
Security Key (U2F)
|
Allows the user to register and use a U2F-compatible security key as a second
factor of authentication. The Register option indicates that a Salesforce admin has
given users in the org the option to register a security key. The Remove option
indicates that the user has registered a security key, and can remove their
registration if needed. |
|
Send Apex Warning Emails
|
Specifies that users receive an email notification whenever they execute Apex
that surpasses more than 50 percent of allocated governor limits.
Available in
Developer, Enterprise, Unlimited, and Performance Editions only.
|
|
Show View State in Development Mode
|
Enables the View State tab in the development mode footer for Visualforce
pages.
This field is only visible to orgs that have Visualforce enabled and
Development Mode selected.
|
|
Site.com Contributor User
|
Allocates one Site.com Contributor license to the user, granting the user
limited access to Site.com Studio. Users with a Contributor license can use Site.com
Studio to edit site content only.
The number of user records with this checkbox
enabled can’t exceed the total number of Site.com Contributor licenses your org
has.
Available in Developer, Enterprise,
Unlimited, and Performance Editions, only if Site.com is enabled for your
org.
|
|
Site.com Publisher User
|
Allocates one Site.com Publisher license to the user, granting the user full
access to Site.com Studio. Users with a Publisher license can build and style
websites, control the layout and functionality of pages and page elements, and add
and edit content.
The number of user records with this checkbox enabled can’t
exceed the total number of Site.com Publisher licenses your org
has.
Available in Developer, Enterprise, Unlimited, and Performance
Editions, only if Site.com is enabled for your org.
|
|
Start of day
|
Time of day that user generally starts working. Used to define the times that
display in the user’s calendar. |
|
State/Province
|
State or province portion of user’s address. Entry is selected from a picklist
of standard values, or entered as text. Up to 80 characters are allowed if the field
is a text field. |
|
Suffix
|
Name suffix of the user, as displayed on the user edit page. Up to 40
characters are allowed for this field.
To enable this field, from Setup, enter
User Interface in the Quick Find box, then select
User Interface. In Lightning Experience, the User
Interface page is the last item under the User Interface node. Then select
Enable Name Suffixes for Person Names.
|
|
Temporary Verification Code
|
Users can enter a temporary code when they forget or lose the verification
method that they usually use for multi-factor authentication. Only Salesforce admins
can generate or expire a temporary code for a user. Users can expire their own
code. |
|
Time Zone
|
Primary time zone in which user works.
Users in Arizona select the setting
with America/Phoenix, and users in parts of Indiana that
don’t follow Daylight Savings Time select the setting with
America/Indianapolis.
|
|
Title
|
Job title of user. Up to 80 characters are allowed in this field. |
|
Used Space
|
Amount of disk storage space the user is using. |
|
User License
|
Indicates the type of user license. |
|
Username
|
Administrative field that defines the user’s login. Up to 80 characters are
allowed in this field. |
| Verified Return Address |
For users who specified a return email address that differs from their user
email address before Spring ’25, this field indicates whether the user manually
verified their return email address. When users specify a return email address in
Spring ’25 and later, this field is always true. |
|
Zip/Postal Code
|
ZIP code or postal code portion of user’s address. Up to 20 characters are
allowed in this field. |
