Document toolboxDocument toolbox

Group Mapping

Owned by Tibor Tasi
Last updated: Sept 07, 2023 by Attila Bordás
3 min read

Group settings

For the proper functionality, License Optimizer requires you to set up login and access groups for your applications.

Please note, all of the login and access groups should be unique, and set to only one application for the most efficient user handling.

 

Login Group

License Optimizer needs to know which group members it can grant access to the application and will be under optimization. This is usually the “confluence-users” providing application access by default. (You can use this default group or could also create a new one for this purpose.)

You should configure this group as “login group” for the License Optimzier app. This group can be read-only groups, since the optimizer doesn't make any changes to that group, it is only using it to determine if a user should have access or not. The size of this group can be bigger than your purchased license tier, since the app will rotate the access of these users based on their activity, thus optimizing your license.

Access Group

Confluence will treat users as licensed users and provide access to them when they are members of the configured groups that are assigned to the “Licensed users” Global Permission. We recommend creating a new group for this, since the selected group here will be manipulated in real-time by License Optimizer and it will remove from or add users to it. This group should be readable and writable.

If you are using LDAP or Active Directory, read the following: LDAP user group settings

After you created this special group, it should be added to the “Licensed users” Global Permission in Confluence administrator settings first with “can use” enabled. We highly recommend to configure administrator group(s) as well so they can log in to the Application anytime regardless the License Optmizer.

Now you should configure this group as “access group” in the License Optimizer, so the app can provide them application access. In the access group picker, only groups that have been added to the global permissions menu will be listed.

The size of this group is calculated by this formula: “your current license tier” - “the size of the groups that are also added in the application access menu for the chosen application”.

Access Limit

With the access limit option, you can set the number of users after which the application should start optimizing, as if it were the maximum number of seats based on the applied license. This can be helpful in some cases, e.g. testing out the app.

  • If empty, the app will starts to optimize after the maximum number of users allowed by the license tier has been reached.

  • If set, then the app treats the provided number as if it were the maximum number of seats that can be assigned (instead of the user tier of the applied license) and starts optimizing users after reaching the value. IMPORTANT: The limit must be less than or equal to the user tier by the currently applied license.

An example of how it works:

  • There is a 100 user tier license applied.

  • There is a fixed admin group of 9 members.

  • In this case by default, LO can assign 91 places for other users.

  • The Access Limit is configured to 50.

  • With 9 fixed admins, the LO sees 41 seats (50 limit - 9 fix user) as allocable.

  • If the number of logged-in users reaches 50, it will start managing the users and rotate them between the assignable 41 seats.

  • The remaining 50 seats in the application will be unused or can be further allocated or assign to fix users.

Removing Application Access from the old group(s)

After you started it and License Optimizer is running without any issue, the only thing left to do now is to remove groups from “can use” permission that are not configured as “access group(s)”.