Study guide

3.5 Identity, Login History, MFA, and Session Risk

Salesforce Admin Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Platform Administrator Orientation and Official Source Control

1.1 Credential Name, Current Outline, and Search Language 1.2 Exam Format, Fee, Score, and Reference Rules 1.3 Trailhead, Trailhead Academy, and Pearson VUE Delivery Workflow 1.4 Domain Weights, Agentforce, and Study Prioritization 1.5 Maintenance Modules, Credential Ethics, and Exam Security 1.6 Developer Edition, Trailhead Playground, and Practice Bank Workflow

2 Chapter 2: Configuration, Setup, User Management, and Org Controls

2.1 Company Information, Fiscal Year, Business Hours, and Locale 2.2 User Records, Licenses, Profiles, Permission Sets, and Login Access 2.3 Login Security, Session Settings, and Identity Basics 2.4 Setup Navigation, Release Readiness, and Change Control 2.5 UI Settings, Home Pages, Apps, and Navigation 2.6 Configuration and Setup Case Lab

3 Chapter 3: Security, Access, Identity, and Sharing Model

3.1 Org-Wide Defaults, Roles, Sharing Rules, and Teams 3.2 Profiles, Permission Sets, Permission Set Groups, and Muting 3.3 Field-Level Security, Page Layouts, and Dynamic Forms 3.4 Record Access Troubleshooting and Login-As Workflow 3.5 Identity, Login History, MFA, and Session Risk 3.6 Data Visibility, Reporting, and Analytics Security 3.7 Security and Access Case Lab

4 Chapter 4: Object Manager, Lightning App Builder, and Data Modeling

4.1 Standard Objects, Custom Objects, and Schema Fit 4.2 Fields, Formulas, Rollups, Validation, and Requiredness 4.3 Lookup, Master-Detail, and Junction Relationships 4.4 Record Types, Business Processes, Page Layouts, and Lightning Pages 4.5 Dynamic Forms, Dynamic Actions, and User Experience 4.6 Schema Change Risk, Data Quality, and Deployment Readiness 4.7 Object Modeling Case Lab

5 Chapter 5: Sales, Marketing, Service, and Support Applications

5.1 Lead, Campaign, Account, Contact, and Opportunity Flow 5.2 Sales Processes, Path, Products, Price Books, and Forecasting 5.3 Case Management, Queues, Assignment, Auto-Response, and Escalation 5.4 Knowledge, Entitlements, Service Console, and Support Productivity 5.5 Sales-Service Data Quality and Automation Boundaries 5.6 Application Configuration Troubleshooting 5.7 Sales and Service Applications Case Lab

6 Chapter 6: Data and Analytics Management

6.1 Data Import Wizard, Data Loader, Export, and Backup 6.2 Duplicate Management, Validation, and Data Quality Controls 6.3 Data Transfer, Ownership, Mass Update, and Mass Delete 6.4 Report Types, Filters, Summary Formulas, and Buckets 6.5 Dashboards, Components, Subscriptions, and Sharing Impact 6.6 Analytics Security, Visibility, and Executive Reporting 6.7 Data and Analytics Case Lab

7 Chapter 7: Automation, Flow, Approval, and Operational Processes

7.1 Automation Tool Selection and Order of Execution 7.2 Flow Builder: Screen, Record-Triggered, Scheduled, and Autolaunched Flows 7.3 Approval Processes, Email Alerts, and Notification Patterns 7.4 Validation Rules, Assignment Rules, and Escalation Rules 7.5 Automation Testing, Debugging, and Governance 7.6 Automation Performance, Recursion, and Maintainability 7.7 Automation Case Lab

8 Chapter 8: Productivity, Collaboration, Mobile, and AppExchange

8.1 Activities, Tasks, Events, Calendar, and Email Productivity 8.2 Chatter, Feeds, Groups, Notifications, and Collaboration Governance 8.3 Salesforce Mobile Navigation, Actions, and Page Design 8.4 List Views, Kanban, Path, and User Adoption Tools 8.5 AppExchange Evaluation, Installation, Permissions, and Risk 8.6 Productivity and Collaboration Case Lab

9 Chapter 9: Agentforce for Platform Administrators

9.1 Agentforce Use Cases, Admin Boundaries, and Fit 9.2 Trusted AI, Security, Data Access, and Permission Implications 9.3 Agent Builder, Prompt Builder, and Grounding Concepts 9.4 Testing, Deployment, Monitoring, and Feedback Workflows 9.5 Agentforce Service, Sales, and Internal Productivity Scenarios 9.6 Agentforce Risk, Troubleshooting, and Governance 9.7 Agentforce Case Lab

10 Chapter 10: Integrated Salesforce Admin Scenario Labs

10.1 New Sales Org Setup Integrated Lab 10.2 Service Team Case Management Integrated Lab 10.3 Data Quality and Analytics Integrated Lab 10.4 Security, Access, and Reporting Integrated Lab 10.5 Flow Automation and Change Control Integrated Lab 10.6 Agentforce and Adoption Integrated Lab 10.7 Full Admin Simulation Strategy

11 Chapter 11: Final Review, Maintenance, and Test-Day Strategy

11.1 Final 30-Day Salesforce Admin Review Plan 11.2 Trailhead Playground Hands-On Drill Plan 11.3 105-Minute Exam Timing, Flagging, and Review Workflow 11.4 Test-Day Checklist: Online or Test Center 11.5 Post-Exam Maintenance Modules and Next Certifications 11.6 Salesforce Admin Final Mixed Review

3.5 Identity, Login History, MFA, and Session Risk

Key Takeaways Explain This Topic AI

User access starts with identity status, authentication, login policy, network policy, session policy, and MFA before object or record permissions are evaluated.

Login History gives admins practical evidence about failed logins, source IP, login type, browser, platform, and failure reasons.

MFA is an identity assurance control and should be handled through approved Salesforce and identity-provider methods, not by weakening user permissions.

Session security troubleshooting separates who authenticated, from where, with which risk controls, and whether the session should remain trusted.

Last updated: May 2026

Identity Comes Before Data Access

A user cannot reach object permissions, record sharing, reports, or Agentforce features until Salesforce accepts the login and creates a session. Identity troubleshooting starts with the user record. Is the user active? Is the username correct? Is the profile assigned? Is the user frozen? Has the password expired or been reset? Are login hours or login IP ranges blocking the attempt? Is single sign-on configured, and is the identity provider sending the expected assertion?

Profiles can include login hours and login IP ranges. Org-level Network Access can define trusted IP ranges. Session Settings can control timeout, session security level, and related behavior. Connected Apps can enforce policies for OAuth-based integrations. Permission sets and session-based permission sets may control access after a higher assurance session is established. These identity controls are related, but they are not the same as role hierarchy or sharing rules.

Symptom First evidence source Likely layer

User cannot log in at all. User record and Login History. Active status, password, SSO, MFA, login hours, IP restriction.

User can log in only from office. Login History and profile IP ranges. Network or profile login IP policy.

User is prompted for MFA more than expected. Session settings, identity provider policy, login type. Authentication assurance and session trust.

Integration fails OAuth login. Connected App policy and login event evidence. App access, IP relaxation, OAuth scope, user status.

User can log in but cannot see data. Permission and sharing review. Authorization, not authentication.

Login History As Evidence

Login History is an admin's first stop for many access tickets. It can show successful and failed attempts, timestamps, source IP, login type, browser or client details, platform, and failure messages. In Setup, search for Login History . For one user, you can also open the user record and inspect related login information where available.

Use Login History to verify the facts before changing settings. If the failure reason points to invalid password, resetting sharing is irrelevant. If the source IP is outside the profile's allowed range, changing a permission set will not help. If SSO is failing, compare Salesforce user federation identifiers, username mapping, certificate validity, identity provider policy, and connected app settings depending on the SSO model.

Login History is also useful after a fix. If a user says the issue remains, confirm whether they attempted a fresh login after the configuration change and whether the failure reason changed. Evidence prevents circular troubleshooting.

MFA And Identity Assurance

Multi-factor authentication adds proof beyond username and password. Salesforce administrators should understand approved MFA methods in the org, enrollment status, recovery procedures, and how MFA interacts with SSO or an external identity provider. The correct support response to an MFA problem is usually to verify enrollment, reset or reconnect the approved verification method, review identity provider policy, or apply an approved temporary access process. It is not to grant broader data permissions.

MFA is sometimes enforced outside Salesforce by the organization's identity provider. In that case, the Salesforce admin still needs enough context to route the ticket. If SSO is the only login path, a user who cannot satisfy MFA may need help in the identity provider. If Salesforce Authenticator or another Salesforce-supported method is used directly, the admin may work from Salesforce setup tools and policy.

Do not promise that one MFA configuration is always current for every org. Administrators should verify the org's current Salesforce security settings, identity provider standards, and company policy. Certification study should focus on the decision logic: MFA raises login assurance; it does not grant record access, field visibility, or object CRUD.

Session Risk And Policy

A session is the authenticated connection Salesforce trusts for a period of time. Session risk controls include timeout, locking sessions to IP address, requiring secure connections, high assurance session requirements, and connected app session policies. Some actions can require a high assurance session, meaning the user must satisfy stronger authentication before using the feature.

Session troubleshooting asks four questions:

Did the correct user authenticate?

Did the login come from an allowed network, device, app, and time?

Did the session meet the required assurance level for the action?

Did the session expire, get revoked, or fail because of connected app policy?

Scenario: A finance admin logs in successfully but cannot access a sensitive setup feature until completing an additional verification step. That points to session assurance, not record sharing. Scenario: A sales rep can log in from the office but fails from a hotel network with an IP restriction message. That points to login IP policy, not field-level security.

Admin Support Workflow

Use this workflow for login and identity tickets:

Confirm the user's exact username and whether the user is active or frozen.

Ask for timestamp, location, network, client, and screenshot of the error when policy allows.

Review Login History for the matching attempt.

Check profile login hours and login IP ranges.

Check org Network Access and Session Settings if the symptom is network or session related.

Check SSO, connected app, and identity provider settings if the login type is federated or OAuth.

Check MFA enrollment, device change, recovery, and high assurance requirements.

Apply the narrowest approved fix and require a fresh login test.

Document evidence and any security exception.

This workflow is safer than changing several settings at once. If you reset a password, relax IP ranges, and assign a permission set together, you may close the ticket but never learn which control mattered. On an exam, that creates the same problem: broad answer choices may sound helpful but fail the specific symptom.

Exam Traps

Authentication and authorization are different. Authentication proves who the user is and whether the session is trusted. Authorization decides what the user can do after login. Login History is about login events, not every record access decision. Role hierarchy does not fix password or MFA failure. Permission sets do not bypass login hours. OWD does not change trusted IP ranges.

Also be careful with integration users. Connected apps, API access, OAuth policies, profile restrictions, MFA or high assurance requirements, and user status can all affect integrations. A good admin uses dedicated integration users or named principals according to company policy, assigns least privilege, monitors login activity, and avoids sharing personal credentials.