Content Comparison

While adding a user you can define the licensing type of that user. This helps on how the user uses the application. For more information about adding users, see Manage Users.

...

Assigning Concurrent user licenses is not restricted, but the number of concurrent users that can log in at the same time must not exceed the specified limit. The number of concurrent licenses a company purchases, defines the maximum number of concurrent license users who can log in to the application simultaneously.

...

1. Navigate to MANAGE> TOOLS> Manage Sessions
2. Select the check box in the first left column to specify the user 
3. Click Log out user.
   

Usage of session for Named users:

A named user can access two web sessions and unlimited mobile sessions at any time. 

Usage of sessions for Concurrent users:

A concurrent user can access two web sessions and unlimited mobile sessions. If the concurrent user log in counts are less than the specified limit, the user gets an alert before logging in.

For example, If the user (Named/Concurrent) is logged in to Intelligent Service Management in the Chrome browser and also in Firefox, the user will not be allowed to log in to Intelligent Service Management in Safari at the same time. The user will get an alert before logging in to the session and will be asked to logout one or both of the existing sessions.

Org-Based License Distribution

Objective: Enable granular license distribution across organizations with strict allocation enforcement for floating/concurrent licenses.

• Multi-Org License Allocation Model
  1. For example, if an organization has 120 total licenses, 50 are allocated to OrgA, 50 to OrgB, and 20 are pooled for use by users in OrgC and OrgD. (e.g., OrgA: 50, OrgB: 50) and a shared pool(e.g., 20 unallocated).
  2. Organizations consume licenses only from their allocated quotafirst; unused allocations remain isolated from other orgs/pool unless explicitly configured otherwise.
• Strict Enforcement Rules
  1. Applies exclusively to concurrent/floating licenses(not perpetual/free licenses).
  2. Users blocked if their organization’s active logins exceed its quota—even if free/pool licenses exist (e.g., Analyst A denied at OrgA’s 50/50 limit despite unused OrgB/pool licenses).
  3. Display an admin alert if 100% of tenant licenses are allocated to specific organizations, leaving zero licenses in the shared pool for unassigned groups/analysts (e.g., allocating all 120 licenses to OrgA/B triggers a warning).
     
     
• Isolated License Availability Checks
  1. Allocated Organizations:
     1. Restrict validation exclusively to the user’s assigned organization quota (e.g., OrgA never borrows from OrgB/pool). Ignore parent/sibling orgs or shared pools during checks.
  2. Unallocated Organizations:
     1. Validate only against pooled licenses. Never traverse hierarchy (e.g., OrgC/D users cannot access OrgA/B’s unused licenses).
        
        
• Org-Based License Validation

           When the Org-based License slice parameter is enabled:

           Step 1: Validate against the user’s primary organization:

1. Allocated organization: Allow login only if active logins < allocated quota (e.g., OrgA caps at 50). Block access with “license limit exceeded” if exceeded.
2. Unallocated organization: Check pooled licenses → Allow login if pool usage < available count; else block with message.

Org based License can be enabled through a config parameter as shown below

Image Added

Once the above parameter is enabled You will see a new tab called "License", so you can allocate the license count

Image Added