Study guide

3.4 Record Access Troubleshooting and Login-As Workflow

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.4 Record Access Troubleshooting and Login-As Workflow

Key Takeaways Explain This Topic AI

Record access troubleshooting should isolate user, object, record, action, interface, and expected source of access before changing configuration.

Broad permissions such as View All, Modify All, View All Data, and Modify All Data can explain access and should be documented carefully.

Login-As is a support and verification tool, not a substitute for understanding permissions or following company privacy and change-control policies.

Edit failures often come from field security, validation, automation, approval locks, ownership, or record type behavior even when the record is visible.

Last updated: May 2026

Troubleshoot The Symptom Before The Setting

A record access complaint usually arrives as a vague statement: I cannot see the account, I cannot edit the case, the report is missing rows, or my manager can see too much. The admin's first job is to turn that complaint into a precise test. Identify the user, object, record, requested action, interface, and expected business reason for access. Then compare actual behavior to the designed model.

Do not start by making OWD more open or assigning System Administrator. Those changes can solve the ticket while creating a security incident. Instead, gather evidence and work through the access stack. In a production org, follow the organization's support, privacy, and change-control rules. In a Trailhead Playground, practice the same sequence with test users so the workflow becomes automatic.

Symptom Likely layers to check Poor shortcut

Cannot find object tab. App access, tab settings, object Read. Changing OWD.

Can open record but cannot edit. Object Edit, record edit access, FLS, layout, locks, automation. Granting Modify All Data.

Can see some records but not others. Ownership, OWD, role, sharing rules, teams, territories, restriction rules. Cloning the profile.

Report missing rows. Record access, report type, filters, folder access, running user for dashboards. Making the report public without row diagnosis.

Field absent everywhere. Field-level security. Dragging field onto layout only.

The Record Access Stack

Use a predictable order. First, confirm the user can log in and is active. Second, check the user's license, profile, permission sets, and permission set groups for object permission. Third, check whether any broad permission explains the result. View All on an object bypasses record sharing for read access to that object. Modify All on an object bypasses sharing for edit and delete style administration on that object. View All Data and Modify All Data are broader org-level permissions and should be rare.

Fourth, inspect the record's owner, OWD, role hierarchy path, sharing rules, public groups, teams, queues, territories, manual shares, and implicit access. Fifth, check newer visibility constraints such as restriction rules where the org uses them. A restriction rule can narrow which records certain users see even when sharing grants broader access. Finally, inspect non-sharing blockers: validation rules, flows, approval locks, duplicate rules, required fields, and page-specific behavior.

Login-As Workflow

Login-As lets an authorized admin open Salesforce as another user to reproduce a reported experience. Setup path commonly starts from Setup > Users > Users , then the Login link where available and permitted. Org settings and policy determine whether admins can log in as users and whether user consent is required. Treat this capability with care because you may see or affect real user data.

A professional Login-As workflow looks like this:

Record the support case, user, expected action, and business owner approval if required.

Review user permissions first so you know what you expect to see.

Log in as the user only long enough to reproduce the issue.

Avoid changing business data unless the support process explicitly authorizes it.

Capture configuration evidence rather than personal data where possible.

Log out of the user session and return to your admin session.

Apply the least-privilege fix in configuration or data ownership.

Retest as the user or with a clean test user.

Document the cause, fix, and any access risk discovered.

Login-As is useful because admins often see more than ordinary users. If an admin tests a page as themselves, a hidden field, private record, or missing tab may look fine. Logging in as the affected user can confirm the symptom. It does not explain the root cause by itself. You still need to inspect the permission sources.

Access Decision Lab

Scenario: Priya is a support agent. She can open Case C-100 but cannot edit Status. Case OWD is Private. Priya is on the case team with Read/Write access, her profile grants Case Read and Edit, and Status is visible and editable by FLS. When she saves, a validation error says Closed cases cannot be changed after manager approval. The access model is probably not the blocker. The save failure is business logic or approval state.

Scenario: Daniel can see every opportunity in the org even though Opportunity OWD is Private and he is not above every owner in the role hierarchy. He has a permission set with View All on Opportunity. That explains read access without changing OWD. If the business does not approve that broad visibility, remove or adjust the permission assignment rather than rebuilding sharing rules.

Scenario: Mei cannot see account A-200. She has Account Read, no View All, Account OWD is Private, she does not own the account, her role is not above the owner, and no sharing rule, team, territory, or manual share includes her. The least-privilege fix depends on business pattern. If she needs one account, add an account team or manual share. If her team needs a category of accounts, use a sharing rule or territory model. If every user should see every account, revisit OWD with stakeholders.

Troubleshooting Checklist

Before closing an access ticket, answer these questions:

What permission source gave or denied object access?

What record sharing path gave or denied record access?

Was any broad permission involved?

Did field-level security or layout behavior affect the symptom?

Did validation, automation, approval, duplicate rules, or locking affect save?

Was the issue reproduced as the affected user or an equivalent test user?

Was the fix least privilege and documented?

This checklist is exam useful because many answer choices fix a symptom at the wrong layer. If the user lacks object Read, sharing will not help. If the user lacks a record sharing path, adding a field to a layout will not help. If a validation rule blocks save, changing the role hierarchy may not help.

Exam Traps

Access is not only see versus cannot see. Salesforce has read, create, edit, delete, transfer, report, export, approve, and administrative actions. A user may be able to view a record, edit some fields, and fail on one operation. Read the verb in the scenario.

Be careful with inherited access. Managers may see subordinate records through role hierarchy. Account owners may receive implicit access to related opportunities, cases, or contacts depending on object relationships and settings. Users in queues may access queued records. A correct answer often comes from recognizing one of these record access paths rather than changing permissions.