- Explain the importance of Salesforce user records.
- Explain the difference between deactivating and freezing a user record.
- Explain how a user can become locked and unlocked.
- Explain the concept of record ownership.
- Describe the capabilities of queues.
- Describe which objects support queues.
- Explain the difference between user and feature licenses.
- Explain how licensing influences what actions a user can perform.
- Explain the implications of user localization settings.
- Describe the translation capabilities of Salesforce.
- Describe the different methods that can be used to authenticate to Salesforce.
- Describe identity verification, and under what conditions it occurs.
- Describe how to monitor and remove activations.
- Describe the security token, and under what conditions it is required.
- Describe the steps required to login as another user.
- Describe a session, and what settings influence sessions.
- Describe how to monitor and remove sessions.
- User Setup – Module Checkpoint
Localization Settings for Salesforce.com Users
Video Must 9m CertifiedOnDemand.com
Objectives for this Resource:
Time zone: determines the offset used to display time references in Salesforce (similar to changing the time zone on your computer).
Currency: can only be selected when multiple currencies is enabled, and will determine the default currency for records created by this user. If currency cannot be selected on the user record, then multiple currencies is not enabled and the organziation’s currency locale will be used to determine how currencies are displayed for all users.
There are multiple tiers of language support in Salesforce. The tier of language support will determine which standard components are translated by Salesforce. Components that are not translated will use the organization’s default language.
- Fully Supported: translates all standard fields, objects, and setup menu
- End User: translates all standard fields and objects, but not setup pages
- Platform Only: no translation of standard objects, field, or setup menu (custom translation only)
Custom fields and objects must be translated using the translation workbench (otherwise the untranslated value will be displayed).
Data (e.g. the name “John Smith” in a lead record) is largely not translated (one exception is picklist values, which can be translated).
Languages support discussed @5m17s