Setup

Users can add their own identity confirmation methods for which they receive email notifications. The added method is not blocked

• A user that’s assigned as the sole recipient of workflow email alert cannot be deactivated

• His records can be transferred to another user

• The deactivated user will not be deleted from the system but will no longer be able to log in to SF

• User is the sole recipient of workflow email alert

• If the user is a default owner of Leads or Cases

• If the user is part of custom hierarchy fields

• Freezing a user does not release the license for use by another user

The My Domain feature allows the use of a subdomain for a SF org to better manage login and authentication.

The company name can be included in the URL

• subdomain must be tested for login problems by using thee new subdomain name to log in.

• tabs and links within the SF org also need to be checked

• application URLs and hard-coded references need to be updated before deployment

• to avoid confusion, the upcoming change should be announced much earlier than the date of deployment

• SF password policies do not apply for SSO users

• SSO users cannot reset their passwords within SF

• Roles are used to create a sharing hierarchy among the users

• Sharing rules can never be stricter than the organization-wide sharing derfaults

IP ranges can be set both Profile-level and Organization-wide, using Login IP ranges and Trusted IP Ranges, respectively.

• However, only the Login IP Ranges setting is entirely restrictive.When the access denied, they see the same message, as if the username or password was wrong.

• Trusted IP Ranges: Users can log in without receiving a login challenge for verification. If a user tries to log in outside the trusted IP Range, they receive an activation code

• reset passwords for users in specific roles

• create users

• assign specific permission sets

• manage custom objects

• 
  

• A Display the standard SF login page

• Display a custom logout page

• Display a custom single sign on page

• can be configured for users by setting the ‘Session Security Level Required at Login‘

• ‘Multi-Factor Authentication‘ should be in the ‘High Assurance ‘ column on the ‘Session Settings‘ page in Setup

• It makes the login page private and accessible only behind a corporate firewall

• It can be configured to use a stronger form of user authentication, such as integration with a secure identity provider

• Multi-factor authentification

• password policies

• trusted IP ranges

A. The profiles available depending on the license type selected

B. the username and email address can be different. except when setting up multiple users

• The average number of logins per user per a specified time period

• who logged in more than the average number of times

• who logged in during non-business hours

• First name, Last name, Alias, username, email, role and user license

• Object permissions

• Page Layouts

• Field Level Security

• ensuring that a record type is available to users

• Controlling which Apex classes and Visualforce pages users can access

• Making certain fields of an object read only for users

• Opportunity team members can be added by Salesforce Administrator, the opportunity owner, and users above the owner in the role hierarchy.

• Opportunity team must be enabled in Setup

• SF Admins or users can create default teams.

• Custom fields can be added to the Opportunity Team Member object

• Yes, access is granted by default to users in a higher role for standard objects

• ‘Grant access using hierarchies‘ is always checked for standard objects such as account and cannot be changed

-> to store

• reports

• dashboards

• files

• email templates

-> pubic group can contain a combination of users, roles, users assigned to specific territories, other public groups and roles, and subordinates in the hierarchy

-> is a least-privilege profile that includes:

• Access Activities

• Chatter Internal User

• Lightning Console User

• View Help Link permissions

• organize reports and dashboards into a logical structure

• folder sharing is at the root level, not subfolder level

• subfolders can be created in user-created folders, but not in Public or Private folder

Record-level sharing is related to:

• organization-wide defaults

• sharing rules

• Roles

Object-level permissions are defined by:

• Profiles and permission sets

the access to the contact will be controlled by the access the user has to the parent, in this case, Account

• must be enabled on the Company Information page by admin

• the corporate currency must be defined

• Currencies must be made active for them to be used

• Reporting and Forecasting can be done in the record currency and corporate currency

• cannot be disabled, once disabled

• User can set their individual currency on the Personal Information page.

  
  

• exchange rates: between active currencies can be set on the Manage Currencies Page

• Dated exchange rates: this can be used by enabling Advanced Currency Management. It is used for tracking the exchange rates at the date oppotys close

determine the times when users are available ( when to escalate a Case) to support customers and are the basis for the computation of support process hours.

Multiple business hours can be defined, but only one can be used as a default

• Gregorian calendar

• can be configured to start on the first day of any month

• cannot be retrieved back to standard structure - can be replicated b choosing a Gregorian calendar

• standard, custom, and third-party components can be added to a Lightning page using the Lightning App Builder.

• Visibility filters can be set for components on Lightning App and home pages to make them dynamic

• Once the home page has been saved, it needs to be activated to make it visible to the users.

• can be assigned as the Org Default, App Default or assigned to an App and Profile combination.

• When editing Home Page for the first time, SF makes a copy of the standard page. This copy can be then customized

• Activity Section: user activity data, such as daily active users, can be viewed separately for Lightning Experience and SF mobile app

  Usage Section: browser usage and page performance data can be viewed separately for Lightning Exp and Sf mobily app

• Lightning App Builder: shows where in the org the desktop record pages are slow

1. Form Factor can be configured to support desktop, phone or both

2. Personalization Settings: Lightning App can be personalizes depending on the navigation style

3. Utility Items: are productivity tools that can be added to an app

1. Change Sets: can be used to migrate metadata

2. Ant Migration Tool: command line utility can be used to move metadata between a local directory and an Org

3. SF Extensions for Visual Studio

4. Salesforce CLI

5. Unmanaged Package: can be used to distribute open-source projects or application templates to any org

Reford type preference in personal settings

• modify the org-wide sharing default setting for the Campaign Member object

-> For this requirement, the org-wide sharing default setting for the Campaign Member object can be set to ‘Controlled by Campaign Member‘. This would ensure that users see only the campaign members whose lead, contact, account to person account records they have access to.

can be added to grant access to users at the same level.

The sharing rule would be based on the record owner and share records owned by one role with users of another role.

• can be used to set whether a field is visible or read-only by Profile.

• It also allows defining field accessibility in places other than the detail page, whether users should be able to access particular field via the detail page, reports, API ets.

• Fields can be set as hidden in the page layout but users will still be able to access the fields in reports, search an list views

• Tab Settings

• Record types and page layout settings

• object permissions

• field permissions

• Use - any user can view and add the Pricebook to Oppty

• View only

• No access - users cannot see Price Books or add them to Opptys unless sharing rules are used to give visibility

• users need to be members of the library (either as an individual users or part of a public group)

• if the users need to have access to a later date, the file can be added to the library, and then the sales public group can be added as members with the appropriate access type at a later date

• with session-based access control, access can be given to users for a specific session. Once the session expires, the access is revoked automatically without having to remove the assignments

• can be used with permission set groups that contain multiple permission sets.

  
  

1. Create, name the tab and select the object

2. Choose the user profiles for which the tab will be available

3. Choose the apps for which the custom tab will be available

allows personalized individual emails to be sent to multiple contacts, leads, or campaign members. Email templates with merge fields can be used to customize each of these emails

• alternative in SF Classic: Mass Email