Read/Write

In that case, Confluence has permission to manipulate the LDAP groups. Both the login and the access group must be an LDAP group. With that permission settings, License Optimizer will work properly.

Creating user group in Jira with Read/Write permission: If you are creating a new group, with Read/Write permission, Please note that LDAP users create LDAP groups and local users create local groups so always make sure to log in with the correct user before creating new user groups.

Read Only with local groups

In this case LDAP users, groups and memberships are retrieved from your directory server and can only be modified via your directory server. You cannot modify LDAP users, groups or memberships via the application administration screens. However, you can add groups to the internal directory and add LDAP users to those groups.

If the access group is a local group then the License Optimizer will work. The login group can be either local or LDAP group, it won’t affect the application.

Read Only

In case the LDAP permission is set to read-only, License Optimizer will not have permission to manipulate the user groups. That means the application won’t be able to work!

If you are providing access to users from Jira with only License Optimizer for Jira, when users log in they will get access to Jira and Confluence at the same time.

• As you can set login and access groups only in Jira, all of the users that are added in login group will be able to access both Jira and Confluence as well.