Log In to Subscriber Orgs
Available in: Enterprise, Performance, and Unlimited Editions |
User Permissions Needed | |
---|---|
To log in to subscriber orgs: | Log in to Subscriber Org |
Multi-Factor Authentication Required to Log In to a Subscriber Org
Starting in Spring ’22, multi-factor authentication (MFA) is required when logging into the License Management Org (LMO). MFA is required only for LMO users who require access to the Subscriber Support Console. This requirement provides subscribers an extra layer of security by verifying the identity of the user accessing their org. You also have more control over which users log in to a subscriber org.
Determine which users require access to the Subscriber Support Console, and then set up multi-factor authentication (MFA) for those users.
Log In to a Subscriber Org
After you’ve logged in to the LMO using multi-factor authentication (MFA), and your subscriber has granted you login access, you’re ready to log in.
- In the License Management App (LMA), click the Subscribers tab.
- To find a subscriber org, enter a subscriber name or org ID in the search box, and click Search.
- Click the name of the subscriber org.
- On the Org Details page, click Login next to a user’s name. You have the same permissions as the user you logged in as.
- When you’re finished troubleshooting, log out of the subscriber org.
Best Practices for Logging In
- Create an audit trial that indicates when and why a subscriber org login has occurred. You can create an audit trail by logging a case in your LMO before each subscriber org login.
- When you access a subscriber org, you’re logged out of your LMO. To prevent your session from being automatically logged out of your LMO when you log in to a subscriber org, use the org’s My Domain login URL.
- Allow only trusted support and engineering personnel to log in to a subscriber’s org. Because this feature can include full read/write access to customer data and configurations, it’s vital to your reputation to preserve their security.
- Control who has login access by giving the Log in to Subscriber Org user permission to specific support personnel via a profile or permission set. See Assign Permissions to the Subscriber Org Console.