Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

VIP.LEAN Floating Licenses needs 3 Parameters to work

...

Jira Group name, where all potential floating users are members. This group don’t have an Jira Software application access (Jira Software)

...

requires three parameters to function:

  1. A Virtual Users Group (= Floating Users) – See below

  2. An Active Users Group – See below

  3. The number of floating

...

  1. licenses to be

...

  1. utilized by the app

...

  1. , allowing administrators to reserve the

...

  1. remaining named licenses for

...

  1. continuous mapping to specific users (

...

  1. Administrators, technical

...

  1. users, users with

...

  1. Rest API access)

VIP.LEAN Floating Licenses dynamically adjusts user membership in the group granting that grants application access, based on their Login events and the Jira activity of the floating users. Inactive users are removed from the group , and re-added once they become active when they try to log in again.

VIP.LEAN Floating Licenses uses this leverages standard Jira Behaviorbehavior:

Jira considers recognizes users as licensed and provides grants access when they are part of belong to configured groups assigned to the installed application on the Application access page. These group members Members of these groups contribute to the licensed users count, limited by subject to the applied license tier.

TypicallyUsually, if you reach the user tier limit is reached, you need to purchase a license upgrade is necessary. This applies is true even if users aren't simultaneously or permanently are not concurrently or consistently working in Jira. However, VIP.LEAN Floating Licenses can provide access to accommodate more users by dynamically adjusting group membership based on active sessions.through a smart mapping during the login process of the virtual / floating users, considering the Jira activity of all previously logged in floating users which includes:

  • Last login time

  • All user Jira activities, forming part of the activity dashboard

Two groups must be defined for VIP.LEAN Floating Licenses to functionoperate:

  1. A "Login groupVirtual Users Group" containing users you want to grant system access. This group can be larger than exceed your license tier by ideally factor 5 and serves as the virtual / floating user pool for the app. This group does not have access to the Jira Software Application and is only read by the app as a starting point.

  2. An "Access group" manipulated Active Users Group" managed by VIP.LEAN Floating Licenses, matching with access to the Jira Software application and adhering to your license tier size and associated with "can use" permission in Global Settings. The app modifies this group by moving copying users between from the "Login group" and the "Access group".

Administrators should configure these groups using the VIP.LEAN Floating Licenses "Group mapping" option.

Initially, the access group is empty. VIP.LEAN Floating Licenses adds users until the user limit is reached, based on the purchased Jira application license tier. Users aren't removed, and they can log in and work without interruption as long as there's space in the license tier.

Once the access group is full, VIP.LEAN Floating Licenses takes action. When a new user tries to log in, it frees up space by removing the most inactive user from the group.

VIP.LEAN Floating Licenses maintains the session of the most inactive user until they're removed from the login group. Thus, a new user attempting to log in while the group is full must wait until another user becomes inactive. Users become inactive if their last action occurs later than the threshold specified in "General Settings." You can set this time based on typical user activity, balancing faster access and preventing undesired deactivation.

...

  1. Virtual Users Group" to the "Active Users Group." during the login process. The seats in this group are limited by a parameter in the app (Max Number of floating licenses). Once this limit is reached, a previous floating user is removed from the group when an inactivity threshold is met. Users with the longest inactivity time are released first.

Administrators should configure these two groups in the VIP.LEAN Floating Licenses "Settings."