Introduction

In this part of the workshop, you will define the profile fields and categories for all users. This field definition is important for the personal customization of other Linchpin apps, such as a customized menu structure, or supporting the search for people based on their expertise. 

Important: These profile fields are a central aspect of Linchpin. They are used for customization, for search, for contact information, employee and telephone directory search, and also for the display of vCards. As this is personal data, the employee representative group (worker's council) must be involved in this workshop.

Questions and tips about user profiles

• User directory - for example Active Directory (AD)
  • Are there one or more existing directories?
  • Can the user directory be linked? Is this allowed?
  • What is the structure of the data? Are important profile fields uniformly maintained e.g. name, telephone number?
• Profile fields
  • Is there a central image directory?
  • Should the images be automatically imported, or should each user add their own image?
  • Does the employee representative group (worker's council) agree to this initial import of data?
• Mandatory fields
  • Which profile fields are mandatory?
  • Which fields will be used for customization?
• Should an organization chart be automatically generated from the user profiles?
• Every profile field must be approved by the employee representative group (worker's council).
• Should Confluence groups be automatically established from profile fields? For example, a Wiesbaden group based on the employees' location. (Dynamic User Group)