How to Log In as Another User in Salesforce
Log in as another Salesforce user to reproduce a permission issue - the Setup route, the permissions required, and how to switch orgs without losing your place.
Updated 2026-09-09
Half of all permission tickets are resolved by seeing the page the way the user sees it. Login As is the shortest route from a vague bug report to a reproducible one.
The feature is straightforward; the friction is everything around it - finding the user, getting back to your own session, and doing it again in the next org.
The steps
- Setup → Users → Users, find the user, and click Login.
- If Login is missing, check that Administrators Can Log In as Any User is enabled in Setup → Security → Login Access Policies.
- Reproduce the issue, then use the Log out link in the banner to return to your own session.
When the Login link is missing
- The org-wide Login Access Policy is not enabled for administrators.
- The target user has not granted login access, in orgs that require it.
- Your own profile lacks Manage Users, which gates the whole Users page.
Switching between orgs and users faster
Admins rarely work in one org. TurboKit keeps multiple Salesforce sessions available and switches between them while keeping the page you are on, which matters when you are comparing the same record across a sandbox and production.
Do it safely
- Login As is logged - your actions are attributed to you in the audit trail, so treat it as a supervised session.
- Never change data while logged in as someone else unless the ticket says to; reproduce, then fix as yourself.
- Log out of the session explicitly rather than closing the tab.
Frequently asked questions
- Does Login As work in Lightning and Classic?
- Yes, in both. The banner and the exit link render differently, but the underlying session behaviour is the same.
- Is Login As recorded in the audit trail?
- Yes. Login history records the delegated login and the administrator who initiated it, so the activity is attributable.
- Can I log in as a user in a production org from a sandbox?
- No. Sessions are per-org. You need the Login Access Policy enabled in each org, and separate sessions for each - which is the friction a multi-account switcher removes.
More from the Admin How-To
- How to Check Field-Level Security in Salesforce FastCheck field-level security in Salesforce without clicking through Setup: where FLS lives, how it interacts with profiles and permission sets, and faster ways to read it.
- How to Compare Two Profiles in SalesforceCompare two Salesforce profiles field by field: the native Setup route, the permission types worth diffing, and how to keep the result auditable.
- How to Create Multiple Custom Fields in Salesforce QuicklyCreate custom fields in Salesforce in bulk - the Setup wizard, metadata deployment, and in-browser field creation - plus the naming rules to settle first.
- How to Write Salesforce Queries Without Knowing SOQL (AI SOQL)Describe the records you want in plain English and get a runnable SOQL query back - how AI SOQL builders work, what to check before you run the result, and where they still fall short.
- Change Sets vs Metadata API Deployments: Which to UseChange sets and Metadata API / CLI deployments solve the same problem differently. Here is when each one is the right choice, and what a change set genuinely cannot do.
- How to Check Salesforce Org LimitsCheck Salesforce org limits - API calls, data storage, file storage, and daily email - from Setup, the limits API, and the browser, before you hit them.
Related reading
- GlossaryWhat Is a Permission Set in Salesforce?A permission set is a collection of settings and permissions that extends a user's access without changing their profile. Permission sets are additive: they g
- GlossaryWhat Is Field-Level Security in Salesforce?Field-level security (FLS) controls which fields a user can read or edit on records they already have access to. It is enforced in the UI, in reports, and in