Last Updated on October 18, 2022 by Rakesh Gupta

Big Idea or Enduring Question:

• How to limit the number of concurrent sessions for a user? 

Objectives:

After reading this blog, you’ll be able to:

• Understand concurrent sessions and how to identify them using Flow
• Limit the Number of Concurrent Sessions with Login Flows
• Use LoginFlow_ForceLogout variable
• Work with Get Records, Delete Records, Assignment, and Screen Elements
• And much more

Business Use case

Rachel Gillett is working as a Junior Developer at Gurukul on Cloud (GoC). She has received the following requirement from the management:

1. Enforce the number of concurrent sessions per user to one.
2. Provide an ability to kill their previous session and start a new session when login-In.

👉 Demo

Automation Champion Approach (I-do):

User Concurrent sessions refer to the number of interactive, UI-based sessions an individual user can have open and active per user account. Users may create multiple user sessions as they log in to an account from different browser types and devices. 

To enhance the security of the overall Salesforce org, an administrator can implement a Login Flow or use the Transaction Security Policy (Requires Salesforce Shield or Salesforce Event Monitoring add-on subscriptions) to limit the number of concurrent sessions for a user.

There are a few possible solutions for the above business scenario. We will use Screen Flow and Login Flow to solve the requirement.

Before we proceed further, let us understand the characteristics of an AuthSession object – It represents an individual user session in your organization.

Field Name	Details
UserId	This user’s Salesforce user ID.
ParentId	The 18-character ID for the parent session, if one exists (for example, if the current session is for a canvas app). If the current session doesn’t have a parent, this value is the current session’s ID.
SessionType	The type of session. Common ones are UI, Content, API, and Visualforce.
UserType	The kind of user for this session. Types include Standard, Partner, Customer Portal Manager, High Volume Portal, and CSN Only.

Before discussing the solution, let me show you a diagram of a Process Flow at a high level. Please spend a few minutes going through the following Flow diagram and understanding it.

Let’s begin building this automation process.

Guided Practice (We-do):

There are 7 steps to solve Rachel’s business requirement using Screen Flow and Login Flow. We must:

1. Define flow properties for screen flow
2. Add a Get Records element to find the logged-in user’s sessions
3. Add an Assignment element to get the count of logged-in user’s sessions
4. Add a Decision element to check whether the count is greater than 1 or not
5. Add a Screen element to display the message and the option to kill other sessions 
6. Add a Decision element to check if the user wants to kill other sessions
   1. If the option is selected:
      1. Add a Get Records element to find the logged-in user’s current session
      2. Add a Delete Records element to kill other sessions 
   2. If the option NOT is selected:
      1. Add an Assignment element to force logout user 
7. Configure Login Flow for Salesforce Platform licensed users  

👉 Consider using custom metadata types to make the number of current sessions configurable. 

Step 1: Define Flow Properties

1. Click Setup.
2. In the Quick Find box, type Flows.
3. Select Flows, then click on the New Flow.
4. Select the Screen Flow option and click on Create and configure the flow. 
5. It will open the flow designer for you.

Step 2: Adding a Get Record Element to Find the Logged-In User’s Sessions 

The next step is using the AuthSession object to find the logged-in user’s sessions. 

1. On Flow Designer, click on the +icon and select the Get Records element.
2. Enter a name in the Label field; the API Name will auto-populate.
3. Select the Auth Session object from the dropdown list.
4. Select All Conditions Are Met (AND). 
5. Set Filter Conditions
   1. Row 1:
      1. Field: UserId
      2. Operator: Equals
      3. Value: {!$User.Id}
   2. Click Add Condition
   3. Row 2:
      1. Field: ParentId
      2. Operator: Is Null
      3. Value: {!$GlobalConstant.True}
   4. Click Add Condition
   5. Row 3:
      1. Field: SessionType
      2. Operator: Does Not Equal
      3. Value: TempUIFrontdoor
   6. Click Add Condition
   7. Row 4:
      1. Field: SessionType
      2. Operator: Does Not Equal
      3. Value: InternalServiceCall
6. How Many Records to Store:
   1. Select All record
7. How to Store Record Data:
   1. Choose the option to Automatically store all fields. 
8. Click Done.

Step 3: Adding an Assignment Element to Find the Count of Logged-In User’s Session 

The next step is to get the logged-in user’s session count. For this, we will use an Assignment element. 

1. Create a Number Variable varN_SessionCount to store the count.
2. On Flow Designer, click on the +icon and select the Assignment element.
3. Enter a name in the Label field; the API Name will auto-populate.
4. Set Variable Values
   1. Row 1:
      1. Field: {!varN_SessionCount}
      2. Operator: Equals
      3. Value: {!Get_Sessions}
5. Click Done.

Step 4: Add Decision Element to Check Whether the Session Count is Greater than 1 or Not

Now we will use the Decision element to check the number variable from step 3 to find if the count is greater than 1 or not.

1. On Flow Designer, click on the +icon and select the Decision element.
2. Enter a name in the Label field; the API Name will auto-populate.
3. Under Outcome Details, enter the Label the API Name will auto-populate.
4. Condition Requirements to Execute Outcome: All Conditions Are Met (AND)
   1. Row 1:
      1. Resource: {!varN_SessionCount}
      2. Operator: Greater Than
      3. Value: 1
5. Click Done.

Step 5: Add a Screen Element to Display the Message and Option to Kill Other Sessions 

1. Under Block Node, click on the +icon and select the Screen element on Flow Designer.
2. Input the following information:
   1. Enter Label the API Name will auto-populate.
3. Check out the video for step-by-step instructions and some tips.

Step 6: Add Decision Element to Check If the User Wants to Kill the Other Sessions or Not

Now we will use the Decision element to check if the user has selected Sign out all other web sessions checkbox in step 5 or not.

1. On Flow Designer, click on the +icon and select the Decision element.
2. Enter a name in the Label field; the API Name will auto-populate.
3. Under Outcome Details, enter the Label the API Name will auto-populate.
4. Condition Requirements to Execute Outcome: All Conditions Are Met (AND)
   1. Row 1:
      1. Resource: {!Sign_out_all_other_web_sessions}
      2. Operator: Equals
      3. Value: {!$GlobalConstant.True}
5. Click Done.

Step 6.1.1: Adding a Get Record Element to Find the Logged-In User’s Current Session 

The next step is using the AuthSession object to find the logged-in user’s current session. 

1. Under Yes Node, click on the +icon and select the Get Records element on Flow Designer.
2. Enter a name in the Label field; the API Name will auto-populate.
3. Select the Auth Session object from the dropdown list.
4. Select All Conditions Are Met (AND). 
5. Set Filter Conditions
   1. Row 1:
      1. Field: UserId
      2. Operator: Equals
      3. Value: {!$User.Id}
   2. Click Add Condition
   3. Row 2:
      1. Field: ParentId
      2. Operator: Is Null
      3. Value: {!$GlobalConstant.True}
   4. Click Add Condition
   5. Row 3:
      1. Field: SessionType
      2. Operator: Equals
      3. Value: UI
6. Sort Auth Session Records
   1. Sort Order: Descending
   2. Sort By: CreatedDate
7. How Many Records to Store:
   1. Select Only the first record
8. How to Store Record Data:
   1. Choose the option to Automatically store all fields. 
9. Click Done.

Step 6.1.2: Add a Delete Records Element to Kill Other Sessions 

1. On Flow Designer, click the +icon and select the Delete Records element.
2. Enter a name in the Label field; the API Name will auto-populate.
3. For How to Find Records to Delete, select Specify conditions.
4. Select the Auth Session object from the dropdown list.
5. Set Filter Conditions
   1. Row 1:
      1. Field: UserId
      2. Operator: Equals
      3. Value: {!$User.Id}
   2. Click Add Condition
   3. Row 2:
      1. Field: ParentId
      2. Operator: Does Not Equal
      3. Value: {!Get_Most_Recent_Session.Id}
   4. Click Add Condition
   5. Row 3:
      1. Field: Id
      2. Operator: Does Not Equal
      3. Value: {!Get_Most_Recent_Session.Id}
6. Click Done.

Step 6.2.1: Adding an Assignment Element to Force Logout User

The next step is to kill the user’s current session forcefully. For this, we will use an Assignment element. 

1. Create a Boolean Variable LoginFlow_ForceLogout. When this variable is set to trueThe user is immediately logged out.
2. Under No Node, click on the +icon and select the Assignment element on Flow Designer.
3. Enter a name in the Label field; the API Name will auto-populate.
4. Set Variable Values
   1. Row 1:
      1. Field: {!LoginFlow_ForceLogout}
      2. Operator: Equals
      3. Value: {!$GlobalConstant.True}
5. Click Done.
6. Add a Screen element with no contents.

In the end, Rachel’s Flow will look like the following screenshot:

Once everything looks good, perform the steps below:

1. Click Save.
2. Enter Flow Label; the API Name will auto-populate.
3. Click Show Advanced.
4. API Version for Running the Flow: 56
5. Interview Label: Concurrent Sessions Exceeded {!$Flow.CurrentDateTime}
6. Click Save.

Almost there! Once everything looks good, click the Activate button.

Step 8: Configure Login Flow for Salesforce Platform Licensed Users  

1. Click Setup.
2. In the Quick Find box, type Login Flows.
3. Select Login Flows, then click on the New.
4. Select the Type from the drop-down Flow.
5. Enter Concurrent Sessions a Name.
6. The next step is to select Flow, User license, and Profile. Follow the steps as shown in the following screenshot:
7. Click Done.

Proof of Concept

Check out the video for a demo: 

Formative Assessment:

I want to hear from you!

What is one thing you learned from this post? How do you envision applying this new knowledge in the real world? Feel free to share in the comments below.