How many field types exist?

Common configuration options

There are several options that apply to every field type. 

Field label

Enter the name of the profile field here.

This is the name your users see in their profiles.

Help text

If you enter any text here, it will appear as a help icon for all users who edit their profiles. Use this field to guide your users.

Only plain text is allowed here (no HTML etc.).

Category

Select the correct category for your profile field. The correct category may be preselected already. Categories act as headings.

Field type

Select the correct field type. Many field types exist. They range from default text areas to date selects or imported LDAP data.

Depending on the field type, users will be able to enter different information into the profile field. In some cases, like with the field type "dependent field", the field value is fix and can not be changed by users.

In profile

Select the Show radio button to display the profile field in the user's profile. 

Select the Hide radio button to hide the profile field in the user's profile.

In vCard REMOVED IN 2.22

Select the Show radio button to display the profile field in the vCard macro.

Select the Hide radio button to hide the profile field in the vCard macro.

Required

Activate the Required checkbox to make a profile field mandatory. This can be useful when the personalization depends on this field or the field is important in some other way.

Required profile fields will be shown inside the Profile Completion Assistant (2.21 and older), if you choose to activate it.

LDAP attribute

If you synchronize your data with an LDAP resource, you can add the respective LDAP attribute name to every LUP profile field type.

If the user exists in the user directory, the LDAP attribute will determine the profile value and the user can not edit this value within Confluence.

If the user does not exist in the user directory (or the LDAP attribute field is empty), the profile field can be edited from within Confluence.

If the user does exist, but the LDAP attribute is incorrect, the profile field will be blank and can not be edited from within Confluence.

XML node name

If you set up an XML field, add the XML node name which should be retrieved for each profile update.

Releated topic: XML import (LUP 2.17)

Text input

Special configuration

Linking

Check the Activate linking checkbox to enable this option.

Linking transforms a normal text field into a link. The entered URL will be shown in every user's profile. Links can not be edited by users.

To hide the link's URL, enter a cover name for the link in the link label field.

Static link

Static links are regular links (for example: https://info.seibert-media.net) to a fix web address.

Dynamic link

Links can also be dynamic. Dynamic, in this context, means that the content of the link changes, depending on the user.

You can create dynamic links with help of profile field placeholders. Every profile field has a key (for example: {confluence.position}). If this key is used as a placeholder inside a link, it will always change to the content which can be found in this field.

Example: 

Let's say every position that can be found in your company has its own page in the "Positions" space. On those pages, users can find out more about their colleagues and their jobs.

Let's create a new text field with activated linking. The name of the text field is "Find out more about my role".

The link will look like this: https://YourConfluenceName.com/display/Positions/{confluence.position}

Now, every time you click this link in a different profile, you will be linked to different pages, because the users' positions vary.

If you click this link inside a profile of a controller, the link will become https://YourConfluenceName.com/display/Positions/Controller.

If you click this link inside a profile of a CEO, the link will become https://YourConfluenceName.com/display/Positions/CEO.

Multiline text

Select

Special configuration

In the section Configure "Select" you can add options to the dropdown menu.

Click on the Add option button. Two fields will appear.

In the left field, enter the name of the option (for example: "Yes, I agree to be photographed.").

In the right field, enter the position of the option inside the menu. The very top position always has the value 0. Every following number is placed below the number before it. If all entries have the same value, the creation order is used.

Multi select

Special configuration

Cascade select

Special configuration

This field type works only with CSV files.

First of all, you have to create a CSV file which contains all relevant data 

Follow these set of rules rules:

• the first line defines the header names of your CSV datasets
• each distinct hierarchy level has to be defined as bundled pair of identifier (ID) + name (label)
• each hierarchy level has it's own identifier (IDs) which has to be unique for the defined name (label) 
• the depth of the hierarchy is represented by the amount of those ID/label pairs within a CSV line
• the amount of lines represents the amount of elements for each distinct hierarchy level

Your are free to use arbitrary names for the header names as well as for your identifier (ID) + name (label).

However, you have to keep a consistence structure within your chosen hierarchy. Also, your CSV files needs to use the .csv file extension.

Here's an example CSV hierarchy of how a user profile field 'Expertise' could look like …

ID_Category,  Category,                 ID_Group,  Group,                     ID_Item,  Item
1,            Business Administration,  1,         Accounting & finance       
1,            Business Administration,  2,         Corporate responsibility
1,            Business Administration,  3,         Resources management
2,            Information Technology,   4,         Adobe Photoshop
2,            Information Technology,   5,         HTML & CSS
2,            Information Technology,   6,         Javascript,                1,        React
2,            Information Technology,   6,         Javascript,                2,        Vue.js

Download this file here: cascade_selection_example.csv

Q&A

What happens, if an user chose a select box stemming from a cascade select import within his Linchpin user profile,
and a new version of the cascade select hierarchy gets imported missing the previously available and used select box?

All choices by users, which are not available with the current version of the imported hierarchy, won't be displayed anymore.

However, the original user choice is still saved and gets restored, once a new cascade select hierarchy has been imported which provides such check boxes again.

Date input

User select

Phone number (input validation)

Instant Messenger

Special configuration

Language select

Country select

Retrieved from LDAP

Special configuration

Dependent field

Special configuration

Special fields

Full name

You can decide how the users' full names are being displayed.

Navigate to Confluence administration → Linchpin User Profiles → Profile Editor → Special fields.

In the text field, enter the profile field keys which should form the full name. Use any of your previously created user profile fields.

For example: {cup.academictitle-1} {cup.firstname-2} {cup.lastname-3} will result in Dr. John Doe.

For this feature to work, you have to configure your LDAP permissions.

Navigate to Confluence administration → Users & Security → User Directories.

Set your LDAP permissions to Read/Write.

Important: Linchpin User Profiles will never write anything back into your LDAP resource. This setting is only needed for the feature to work. The data is used in a "read-only" mode.

Profile picture sources - URL, LDAP or Confluence

Profile pictures are a special kind of a profile field. They can be taken from three sources: URL, LDAP or direct upload to Confluence.

For a detailed guide on configuration and general information, please see the documentation on profile pictures.