Documentation's navigation

On this page

Org Charts

You can now display a visual representation of your connections to other users (superior / subordinates) in the new "Org Chart" tab in your user profile (if the profile fields are configured accordingly by your administrator).

You can move the Org Charts via drag & drop.

Use the arrow buttons next to the user cards to open or close single branches of the Org Charts.

Use the slider to control the zoom level.

The Center view button will center the Org Charts on yourself.

The Reset view button will reset all changes you made (positioning, zoom level, opening new branches) and display the default view.

Please note that if Space Privacy is active on your instance, only members of the internal group will have access to Org Charts!

More information about internal groups can be found in our Space Privacy documentation.

Configure Org Charts

Navigate to Confluence administration → Linchpin → User Profiles → Org Charts.

Activate Org Charts

For Org Charts to work at all, you need to activate the Activate hierarchical Org Chart slider.


For Org Charts to work, you have to configure which profile field holds the information about superiors/subordinates.

In the Superior section, select the profile field which you configured as a "superior indicator". Click on the Save button to save your changes.

If there is no entry you can choose from, the administrator first needs to add a profile field with the field type "User select" in the Profile Editor.

Top position

NEW IN 2.25.1

This option needs to be configured for Org Charts to be displayed within the People Directory.

In this field, enter the user(s) who do not have any superiors and therefore are at the very top of the hierarchy.

To view the Org Chart, navigate to the people directory. Click on the Org Chart button located in the sidebar on the left side.

If you entered more than one superior, you will see tabs for every respective superior, labeled with their names. Each tab features the Org Chart of the respective superior.

Org Charts and LDAP sync

When importing values into user select profile fields, like when using Org Charts, make sure that the directory attribute contains the user reference as a DN (distinguished name).

This means that the superior has to be referred to via their DN (distinguished name).

The distinguished name (DN) usually has a format like this: cn=user,dc=domain,dc=name.

If a display name (clear name) is used, functions depending on the user select profile field won't work. In this case, the superior won't be displayed.

The Org Chart macro

NEW IN 2.25.1

You can display the Org Chart on any page, now.

Linchpin User Profiles 2.25.1 features a brand new Org Chart macro.

Insert the macro into any page and configure it to display an Org Chart wherever you want.


In the Top position input field, enter the supervisor whose team/department you want to display.

If you wish to display the whole organization, for example, enter the CEO (there's probably no one above the CEO).

In the Depth section, select how many hierarchical levels should be displayed initially by the macro. Those depth levels can be changed anytime when viewing the Org Chart.

Finally, enter the desired height of the macro in pixels (px).

Once you're done, click on the Insert button and publish the page.

Good to know

XML sync and case sensitivity

Both XML sync and Linchpin User Profiles functionality are case sensitive as far as usernames are concerned! Please make sure that the username which is synced via XML corresponds to the case style your colleagues use within their profile field configuration.

An XML sync will import the given values, e.g. exported from an AD or other data source, exactly as given and not perform case-insensitive matching to users. This means that should these values not be identical, a function might not work as intended and search queries in structural charts will not be able to find those users.

Let's take a look at Org Charts. If the supervisor is called Dirk Example, and the users enter Dirk.Example as their supervisor's username, the user needs to be called exactly Dirk.Example within your XML source as well (please note the large initial letters, which are also called Upper Camel Case). If Dirk Example instead were named dirk.example (with small initial letters) in your XML source, the import would succeed, but queries from Org- and Structural Charts won't display relations involving this user, resulting in unexpectedly missing user information.

Configure the displayed profile field

Below the full name of all displayed users, there is one line of additional profile information that's displayed in the user panels. To determine which profile field should be displayed, Linchpin User Profiles looks for the field that is configured as subline in the profile header. For more details, refer to our Subline in Profile header documentation.

Problems when using hidden profile fields

A profile field that's configured as hidden in the profile editor of Linchpin User Profiles will, for technical reasons, not be able to resolve any relation other than finding direct superiors. (such as displaying a user's subordinates or same-level 'siblings'). This is due to the current implementation of hidden fields, which are not written into the Confluence search index and thus cannot be found by CQL queries.

For org charts, this means that if the selected profile field is configured as hidden, the resulting charts will be missing many user connections. Using a hidden profile field to determine org chart relations is thus not recommended.

Looking for an alternative in the Cloud? 

Besides offering apps like Linchpin Intranet Suite, that is available for Atlassian Data Center, we also have apps for Confluence Cloud in our portfolio.

Like Mantra, the intranet for Confluence Cloud, developed by our joint-venture AppAnvil (known for hits like Aura & Karma).

Test the intranet for Confluence Cloud now for free: 

Discover Mantra

This page was last edited on 06/05/2024.