---
schema_version: "1"
id: 2608c509c7db2559336cb8b2271a9ec6d1d5c1893ca82ab775544a085c3b5b5c
title: Gotchas If Users Switch Between Lightning Experience and Salesforce Classic
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/lex_switching_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.lex_switching_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 9c6dfa030e5fff02c67ec2fb7725541c6fc6595184aca754dead1f3e35920464
description: Switching between Lightning Experience and Salesforce Classic affects the underlying URL routing logic and can lead to some unexpected results when links are resolved. There can be snags with bookmarks and sharing links in emails or Chatter posts—especially if only a subset of your users are working in Lightning Experience.
products:
  - Salesforce Platform
  - Cross Cloud
release: "264"
---
# Gotchas If Users Switch Between Lightning Experience and Salesforce Classic

Switching between Lightning Experience and Salesforce Classic affects the underlying URL routing logic and can lead to some unexpected results when links are resolved. There can be snags with bookmarks and sharing links in emails or Chatter posts—especially if only a subset of your users are working in Lightning Experience.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Group</strong>, <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr></tbody></table>

The Lightning Experience User permission and a user’s default interface affect the way links resolve for each user in your org. A user’s default interface isn’t static.

- A user’s _initial_ default interface is determined by when they were added to Salesforce.
    - All users who existed at the time Lightning Experience was enabled in your org keep Salesforce Classic as their default interface. This is true whether an existing user already had the Lightning Experience User permission or is assigned the user permission at a later date.
    - Users who are added to your org after Lightning Experience was enabled get Lightning Experience as their default interface at the time they’re assigned the Lightning Experience User permission.
- If you switch a user to Lightning Experience, their default interface resets to Lightning Experience.
- Any time someone uses the Switcher, that user’s default interface resets to the current environment.
- When switching from Classic to Lightning Experience, if the URL contains `nooverride=1` in Classic, it changes to `nooverride=true` in Lightning, and you don’t see overrides for the record you’re navigating to.
- Running Classic and Lightning Experience in different browser tabs or windows is not supported and can cause unexpected behavior in the look and feel of your org and the values returned by the $User.UITheme and $User.UIThemeDisplayed fields. For example, if your org is using Lightning Experience, but you switch to Classic in a different browser tab, these fields return a Classic theme in both tabs.

Here are the typical link routing interactions your users can encounter.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
      <colgroup>
        <col style="width:25.06203473945409%">
        <col style="width:25.31017369727047%">
        <col style="width:49.62779156327543%">
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="col" class="slds-cell-wrap" style="text-align:center;vertical-align:top;" id="d41204e123">User Has the “Lightning Experience User” Permission?</th>
          <th scope="col" class="slds-cell-wrap" style="text-align:center;vertical-align:top;" id="d41204e126">User’s Default Interface</th>
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d41204e129">Where Links Open</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="User Has the “Lightning Experience User” Permission?" class="slds-cell-wrap" style="text-align:center;vertical-align:top;" headers="d41204e123 ">Yes</td>

          <td data-label="User’s Default Interface" class="slds-cell-wrap" style="text-align:center;vertical-align:top;" headers="d41204e126 ">Lightning Experience</td>

          <td data-label="Where Links Open" class="slds-cell-wrap" style="vertical-align:top;" headers="d41204e129 ">
            <p>For pages supported in Lightning Experience, links open in the new interface
              (even for links generated in Salesforce Classic).</p>
            <p>Links to unsupported pages are
              directed to Salesforce Classic, which opens in a new tab. This temporary redirection
              doesn’t change the user’s default interface to Salesforce Classic. The next time the
              user selects a link that is supported in the new interface, the Salesforce Classic
              tab is reloaded to open the link in Lightning Experience.</p>
            <p style="margin-bottom:0;">To
              share a Lightning Experience link with other users, make sure that they are logged
              in to Salesforce first. Otherwise, the link prompts them to log in and then directs
              them to the home page.</p>
          </td>

        </tr>
        <tr class="">
          <td data-label="User Has the “Lightning Experience User” Permission?" class="slds-cell-wrap" style="text-align:center;vertical-align:top;" headers="d41204e123 ">Yes</td>

          <td data-label="User’s Default Interface" class="slds-cell-wrap" style="text-align:center;vertical-align:top;" headers="d41204e126 ">Salesforce Classic</td>

          <td data-label="Where Links Open" class="slds-cell-wrap" style="vertical-align:top;" headers="d41204e129 ">
            <p>Links usually open in Salesforce Classic.</p>
            <p style="margin-bottom:0;">If a link was generated in Lightning
              Experience, the link opens in Lightning Experience. The user’s default interface
              doesn’t change to Lightning Experience.</p>
          </td>

        </tr>
        <tr class="">
          <td data-label="User Has the “Lightning Experience User” Permission?" class="slds-cell-wrap" style="text-align:center;vertical-align:top;" headers="d41204e123 ">No</td>

          <td data-label="User’s Default Interface" class="slds-cell-wrap" style="text-align:center;vertical-align:top;" headers="d41204e126 ">Salesforce Classic</td>

          <td data-label="Where Links Open" class="slds-cell-wrap" style="vertical-align:top;" headers="d41204e129 ">
            <p>Links open in Salesforce Classic only.</p>
            <p style="margin-bottom:0;">If a link was generated in Lightning
              Experience, the link doesn’t open, because the user can’t access Lightning
              Experience.</p>
          </td>

        </tr>
      </tbody>
    </table>

Given these routing behaviors, you can see the potential for confusion when users share Lightning Experience links with Salesforce Classic users. To minimize link issues, give Lightning Experience access to all users who work closely together. And train your Lightning Experience users to understand how links and bookmarks work across the two experiences.

To avoid link issues altogether, move your entire org to Lightning Experience and turn off access to Salesforce Classic for everyone.

#### See Also

- [Give Users Access to Lightning Experience](https://help.salesforce.com/s/articleView?id=xcloud.lex_enable_users.htm&release=264.0.0&type=5 "When you’re ready to go live with Lightning Experience, it’s not necessary to enable or otherwise turn on the interface. Instead, simply make sure that the appropriate users have access via the Lightning Experience User permission. If you’re rolling out Lightning Experience in phases, set up access for the users in your first group (and so on). If you’re doing a “big bang” rollout, set up access for everyone in your org.")
- [Salesforce Classic Doesn’t Go Away When You Move Users to Lightning Experience](https://help.salesforce.com/s/articleView?id=xcloud.lex_switching_uis.htm&release=264.0.0&type=5 "Saying hello to Lightning Experience doesn’t mean saying goodbye to Salesforce Classic. You and your users can easily move between the new and classic interfaces as needed. So even if Lightning Experience isn’t a perfect fit yet, there’s no risk in rolling it out. Some occasional switching is worth getting the productivity benefits from the new experience.")