Admin: Project Group Config
- Vladyslav Zacharko (Unlicensed)
Project Group Configuration
Group
Privileged User
Privileged User is required in order to perform some low level operations such as group removals. Normally done under a human user context, a user with sufficient privilege to perform that action is required.
Group Actions Permitted
Options are Yes or No. Choose whether you want to allow Project Administrators the ability to perform add/remove operations on groups specified via group matching (see below)
Delegated Group Actions Permitted
Options are Yes or No. Choose whether you want to allow Administrators the ability to delegate management of a group to other groups/users, or Project Administrators the ability to add/remove users from said delegated groups in the space view.
Project group pattern
Specify a group name prefix and/or suffix for all groups that are to be manageable by Project Administrators. These fields should include projectkey somewhere, which is a special term replaced with the contextually available Project key when admins use PUM. Changing this key will be immediate, and will prevent admins from finding and managing any group matching the old format.
Max Number of UserIds to Act On at One Time
Sets the limit of how many users a Project Administrator can add at one time.
Max Number of GroupIds to Act On at One Time
Sets the limit of how many groups a Project Administrator can create at one time.
User
Disabled User Visibility
Choose whether to hide disabled users in PUM tables or show them but add a “deactivated” flag to the end of their table entry.
User Group Filter
Select which group you would like to visually filter by in PUM table views, any users not belonging to a selected group will have a ‘FILTERED GROUP’ flag added to any PUM table entry.
Auto join groups
Possibly refer groups here that any user who is added to a PUM group should be also added to
User Search Enabled
Options are Yes or No. Setting this to Yes allows Project Administrators to perform user searches when defining users for an operation (adding to a group for example). This is useful as it means Project Administrators do not have to rely on knowing the exact details of the users they are looking for. However, you may want this set to No if there may be security measures in place meaning that you do not want Project Administrators to see all users in Confluence.
Example showing how specific Directories can be included in user searching
Customize User Search Directories
By default, PUM will use Jira default search for users that includes all configured User Directories. Its possible that a broken directory (intentional or other) will cause the search to fail. PUM provides the ability to select from defined User Directories, those which should be queried for users. If a custom search is set, at least one User Directory needs to be set, otherwise default search behaviour will result.
Example showing LDAP used to source user data
Cache Expiry is a Data Centre feature only.
Cache Expiry
Configuration | Set the duration of which the Configuration cache will expire. The default value is 24 hours. |
Project Groups | Set the duration of which the Space Groups cache will expire. The default value is 12 hours. |
Delegated Groups | Set the duration of which the Delegated Groups cache will expire. The default value is 5 minutes. |
General
Use Redirects to Refresh Group Membership
Options are Yes or No. Choose whether redirects occur when refreshing group membership views in your browser.
Add-on Deactivated
Prevents usage of the add-on. While this may sound like an unnecessary duplication of the standard way of disabling the add-on, it can be useful as this way allows you to specify a downtime message which is not currently possible through normal disabling.
Add-on Downtime Message
The message that is shown when the add-on has been disabled using the Plugin Deactivated setting mentioned above. If left blank, a default message will be used. The field does not currently support wiki syntax.
Once you are happy with the configuration, click the Save button located at the bottom of the configuration page.