Content |
|
|
The plugin is available at the Atlassian Marketplace. To install the plugin, log in as system administrator and navigate to the global administration (cog icon 
or Browse > Confluence Admin). Enter the Plugins section and navigate to the "Install"-Tab". Search for "User Profile Plugin" and press "Install".
If the installation was successful, a new item should appear on the left-hand panel in the "Administration" section: "User Profile Configuration". This is where the customization of the user profiles takes place. If this link is not visible, please ensure that all required modules of the plugin are enabled. You can do this by clicking "Plugins" in the global administration and selecting the "User Profile Plugin". Of the listed, modules only the modules named "profile" are not required for the plugin to work. Each other module should be enabled.
When upgrading to version 1.9, all profile data will be migrated to a new storage format. This is necessary because Confluence 5.3 allows changing usernames. This process may take several minutes, depending on the number of users and additional profile fields. The detailed progress is logged into the Confluence log file ( |
Background-Knowledge: The profile-Macro (which is a part of the bundled plugin "Profile Macros") is required to display user data at the people directory, the hover for users and at the personal space. The User Profile Plugin provides its own version of this macro. This version behaves like the one from "Profile Macros", but displays additional created user profile elements too. To benefit from all features of the User Profile Plugin the macros should be exchanged.
It is important, that you keep the order of the steps, meaning first disable the standard profile macro and afterwards enable the User Profile macros! |
The plugin needs a valid license to have all the provided features working. Valid licenses are either full licenses, renewal licenses, or 30-day trials and are available at the Atlassian Marketplace. The license model is the same as Atlassian uses for its products - for further information see Atlassians docmentation.
To get a license and provide it for the plugin, please carry out the following instructions, (also see the screenshot below):
Workaround (if one of the steps above does not work or is not available - this may happen with older Confluence versions)
or Browse > Confluence Admin).Without a valid license, the user profiles shows the message "Plugin is not licensed" instead of the user profile data.
Several Configurations can be made, that are listed below .....
You can access the configuration via the menu item "User Profile Configuration" in the panel on the left side of the administration section (cog icon or Browse > Confluence Admin).
The configuration page allows you to add new elements for user profiles or to edit existing elements. This includes standard elements of the user profiles. The standard elements "Full Name" and "Email" cannot be manipulated in order to protect important system functionalities, therefore they are not available in the configuration. Additional elements are placed at the end of the sections Personal and Company. You can change the order of the fields by clicking the arrows. With one click you move the profile element one position up or down. The order of the About Me field cannot be changed since it is never displayed as part of the profile card.
This configuration will be used for all user profiles in the system.
The configuration page of an element allows you to create/edit an element of the user profile.
%%LDAP attribute%% (i.e. name of an LDAP attribute enclosed in %%).%%street%% %%number%% in %%city%%)%%upp_delete_value%% as a placeholder to delete the data for a synchronized profile element.Style: custom
|
Demo of user profile configuration
|
There are 3 ways a synchronization can happen: Periodical or manual for all users (full synchronization), or at login for a single user. During this process, the data of a users profile elements is updated with the values from the configured LDAP repositories according to the mapping that was defined during configuration of the profile fields.
The synchronization is only working in one direction. Data will only be pulled from a repository and will never be written back. This also applies to repositories which are configured as "Read/Write". The synchronization is currently not working for directories of type "Apache Directory Server (ApacheDS)". |
The manual synchronization can be started from the configuration menu. There is a button "Start synchronization" below the profile elements list. After clicking it, a full synchronization will happen. This means that the profile for every user will be synchronized according to your configuration. After the synchronization a short summary will be shown.
Since a full synchronization is a resource consuming task, it should not be started during business hour! |
A full synchronization will be executed periodically. The plugin is configured to start this synchronization by default at 1:11 a.m. each night.
You can customize or disable periodical synchronization via "Scheduled Jobs" in the administration. Look for the entry "External User Directory Sync Job" to configure the job that schedules periodical synchronizations. |
Whenever a user logs in, his profile data is synchronized with the user repository. Note that the synchronization will only run for that single user.
Demo of synchronization:
|
Starting from a particular user, the hierarchical relationships with superiors, colleagues and employees are visualized. The organizational charts contain the full name of the person displayed with a link to the profile, the user picture, as well as the department and the position.
The organizational charts are calculated based on the data the user enter in their profile. One field has to be selected which defines the hierarchy (see the orange marking the screen shot below).
Only elements of type "Userfield" are available for selection. All information about superiors, colleagues and employees is automatically calculated based on that field. |
Additionally the the behaviour of the organization charts that are embedded on the user profile page and in the sidebar of the users personal space can be configured as pictured in the screen shot below. Go to the "User Profile Configuration" in the panel on the left side of the administration section (cog icon or Browse > Confluence Admin). The Organization Chart Configuration can be entered by clicking the button "Configure Organization Charts" below the profile elements list.
| If you are using Organization Charts with an external user directory, you have to get sure that the synchronized field only contains the username as plain text. Using distinguished fields (e.g. manager) will not work. |
Displayed hierarchy is outdated
Organization charts are stored in a cache, which is refreshed periodically (if needed). This means that the organization charts displayed by the macro will not be up to date until the cache is refreshed. The default refresh period is 30 minutes. Depending on how many users are in your instance, the refresh itself may take from some milliseconds for less then 100 users up to several minutes for 10k users or more. So users might notice outdated hierarchies.
The following scenarios might occur:
The refresh of the cache is managed by a scheduled job. If you need to force a cache refresh you can run the job manually. For more details on where to find the scheduled jobs and how to run them manually please refer to the documentation provided by Atlassian. The job is called "Org Chart Cache Updater".
Macro renders an error
As long as the profile element, which defines the hierarchy, is not configured, the macro will render an error.
The plugin allows you to export all user profile data. You can find the following option at the bottom of the "User Profile Configuration" page at the administration (cog icon or Browse > Confluence Admin) .
Via the "Configure export" button, you can define criteria with Lucene search syntax to filter the users that will be exported. Leave the filter field empty to export all users.
If you click "Generate export now", you create a new export with the current export filter, which can be downloaded. But be aware, generating a new profile export may take some time.
"Download last export" allows the last written export CSV file to be downloaded and stored on your local computer.
| A CSV export file is automatically generated after the periodical user synchronization job has finished using the defined export filter! |
The plugin allows you to configure which user is considered as being an "active" user. Only active users are synchronized, exported and considered for organization charts. This is useful if your user repository has users that are not real users - like rooms or computers. You can choose between two policies:
| Users from LDAP directories, which are not yet visible, will be "activated" during synchronization. This means that afterwards they are present in the people directory and can be found when searching. |
This configuration is available by clicking the button "Configure User Policy" below the profile elements list of the "User Profile Configuration" page at the administration (cog icon or Browse > Confluence Admin) .
Uninstall the User Profile Plugin via "Global Administration" -> "Plugins"
Enable the “profile” Macro Module of the “Profile Macros” Plugin :
Open the old plugin administration view via http://<server base url>/admin/viewplugins.action
Select the "Profile Macros" plugin and enable Profile Macros
for the profile-Macro if it had been exchanged
