Study guide

2.3 Login Security, Session Settings, and Identity Basics

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

2.3 Login Security, Session Settings, and Identity Basics

Key Takeaways Explain This Topic AI

Login security combines password policies, multi-factor authentication, trusted ranges, profile login IP ranges, login hours, session settings, and identity configuration.

Trusted IP ranges and profile login IP ranges solve different problems, so admins must know whether they are reducing verification prompts or blocking access.

Session settings govern how long authenticated access persists and when a higher assurance level is required for sensitive actions.

Identity basics such as My Domain, single sign-on, connected apps, and login history help admins diagnose access without weakening security.

Last updated: May 2026

Login security is layered control

Authentication answers who is trying to enter Salesforce. Authorization answers what the authenticated user can do. Session control answers how long and under what assurance level the authenticated session remains valid. Setup scenarios often mix these ideas, and the wrong answer usually comes from treating all access failures as profile problems.

Start with evidence. Setup > Users > Login History shows login attempts, status, source IP, login type, and failure reasons. Setup > Security > Session Settings controls timeout behavior, session security levels, clickjack and content protections, and related session policies. Setup > Security > Network Access stores trusted IP ranges. Profiles can also include login hours and login IP ranges. Connected Apps add another layer for OAuth and external client access.

Passwords are only one part of the login story. Password Policies let admins define expiration, history, complexity, lockout behavior, and related controls. Multi-factor authentication adds a second verification factor and is a major expectation for modern Salesforce access. Admins should not solve repeated login challenges by weakening password or verification settings for everyone. First find whether the friction is caused by a location, device, SSO policy, session timeout, or user education issue.

Security control comparison

Control Setup area What it does Scenario trap

Password Policies Setup > Security > Password Policies Sets password and lockout rules Does not grant object access.

Network Access trusted IP ranges Setup > Security > Network Access Marks IP ranges as trusted for login verification behavior Not the same as blocking all other IPs.

Profile login IP ranges Profile settings Restricts where profile users may log in from Can block valid users outside the range.

Login hours Profile settings Restricts when profile users may log in Time zone interpretation must be checked.

Session timeout Setup > Security > Session Settings Controls inactive session duration Does not fix missing permissions.

Connected app policies App Manager or Connected Apps Controls OAuth app access and session policy Mobile and integration users may be affected.

Trusted IP ranges and profile login IP ranges are a classic exam trap. A trusted range can reduce additional verification challenges for logins from known networks. A profile login IP range can prevent users with that profile from logging in outside approved ranges. If a question says users are blocked when they travel, inspect profile login IP ranges. If it says users are prompted for extra verification from a new office, inspect trusted ranges and identity verification behavior.

Session timeout is another place where admins need judgment. A short timeout can protect sensitive data on shared or mobile devices, but it can frustrate users who work from long forms or dashboards. A long timeout improves convenience but increases risk if devices are unattended. The right answer depends on data sensitivity, device posture, compliance requirements, and user workflow. For sensitive permissions, high assurance session requirements may be more precise than making every session extremely short.

My Domain is foundational for modern identity features because it gives the org a branded, unique login domain and supports several authentication and security capabilities. Single sign-on can centralize authentication through an identity provider. That does not mean Salesforce permissions disappear. A user authenticated through SSO still needs the correct license, profile, permission sets, role, and sharing access inside Salesforce.

Connected apps deserve attention because many login problems are not browser login problems. A user may access Salesforce through the mobile app, an integration, a data tool, or an external application using OAuth. Connected app policies can restrict users, require approval, set refresh token behavior, or enforce session policies. Before changing global session settings, ask whether the issue affects all login methods or only one connected app.

Agentforce and AI-related access should be treated as a governed identity surface. Admins may need to know which users can configure agents, test actions, access grounding data, or monitor usage. Do not use an AI feature to bypass the security model. If an agent or assistant can surface data, the admin must understand whose access is being used, which permissions apply, what audit data exists, and whether the use case is appropriate for automation or should remain a human review path.

Login troubleshooting workflow

Confirm the exact error, login method, time, user, browser or app, and network location.

Review Login History for status, source IP, and failure reason.

Check whether the user is active, frozen, locked out, assigned the correct license, and inside allowed login hours.

Compare the source IP with profile login IP ranges and trusted network ranges.

Review SSO, My Domain, connected app, and multi-factor requirements if the login uses identity integrations.

If login succeeds but work fails, move to authorization: profile, permission sets, role, sharing, field security, and app access.

Hands-on practice should include deliberately creating a safe, limited login policy in a sandbox or Developer Edition org. For example, set login hours on a test profile, observe the effect with a test user, and then remove the restriction. Review Login History after both attempts. This is better than memorizing labels because it shows how Salesforce records the event and how a real admin would troubleshoot.

The exam angle is to preserve security while restoring legitimate access. If only one user is locked out, resetting the password or unlocking the user may be enough. If all users on one profile fail from home, profile IP ranges may be the cause. If mobile access fails but browser access works, inspect connected app policy. If users can log in but cannot view account records, stop looking at authentication and troubleshoot authorization.