Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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)

  • Jira Group name, where the floating user should be added automatically after a successful login . This group must have access to the Jira Software application.

  • The number of floating license to be used by the app. This allows the administrator to reserve the rest of named licenses for a continuous mapping to users (Administrator, technical Users, users with RestAPI Access)

VIP.LEAN Floating Licenses dynamically adjusts user membership in the group granting application access, based on their Jira activity. Inactive users are removed from the group, and re-added once they become active again.

VIP.LEAN Floating Licenses uses this standard Jira Behavior:

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

Typically, if you reach the user tier limit, you need to purchase a license upgrade. This applies even if users aren't simultaneously or permanently working in Jira. However, VIP.LEAN Floating Licenses can provide access to more users by dynamically adjusting group membership based on active sessions.

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

  1. A "Login group" containing users you want to grant system access. This group can be larger than your license tier and serves as the user pool for the app.

  2. An "Access group" manipulated by VIP.LEAN Floating Licenses, matching your license tier size and associated with "can use" permission in Global Settings. The app modifies this group by moving users between 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.

In summary, VIP.LEAN Floating Licenses maximizes license tier usage and dynamically allocates access as needed, without disrupting existing users' work or access.

  • No labels