User Management (Forge)

If the source groups for the project permissions are to be retained, the product access of the respective source group must be removed before copying the users.
The IUM user group must be defined in the global settings of IUM.
Users who receive Jira access through another group or suspended users will not be synced into the IUM user group.

Displays the number of existing IUM users and the maximum allowed number of IUM users in the IUM user group.

Select source group(s)
Set “Run every”
Save Configuration
- The configured sync will be executed after the set interval.
- Alternatively, the sync can also be performed manually without a set interval.
Reset Configuration
- Removes the set job
- Removes existing users from both IUM groups
- Already selected source groups must be removed manually using the x.

If changes have been made during a sync run, this will be displayed in the job execution log.
If users from the ium user group have been suspended in the meantime, or have received a Jira license via another group, they will be automatically removed from the ium user group during the next usersync run.

User added
Number of users added to the ium user group during sync
User filtered out during sync
Number of users who have a fixed Jira license or are suspended and therefore were not synced.
User removed
Number of users who have been removed from the source group since the last sync and have now been removed from the ium user group.
User removed by filter
Number of users who were removed from the ium user group because they were suspended in the meantime or obtained a Jira license through another group.

This message appears if the sync was not completed because this would have resulted in exceeding the allowed number of IUM users.

If an email address is provided for notifications, the recipient will receive an email daily in case of problems.