User extended attributes¶
Admin → Users → User extended attributes defines extra fields for user profiles: the ones your organisation needs but the product does not ship, such as an employee number, a cost centre, or a shift.
Creating an attribute; the identifier and the name must be unique.
Create an attribute¶
| Field | Rule |
|---|---|
| Identifier | Internal name, unique. A duplicate is reported on the field |
| Name | What users see, unique as well |
| Type | Text, number, date, or a dropdown with a list of options |
| Options | Only for the dropdown type: the values users can choose |
| Required | Whether the field must be filled in the user form |
Where it appears¶
Defined attributes show up in the Extended attributes section of the user form, for every user, according to the type and the required flag. Changing an attribute later does not rewrite the values already stored: existing users keep what they had and are asked for the new field when they are edited.
Edit and delete¶
- Edit changes the name, the type, or the options.
- Delete asks for confirmation and removes the field from the user form. The stored values are removed with it, so export what you need first.
Limits worth knowing¶
- A dropdown cannot be changed into free text without losing the stored options.
- An attribute that is required applies to new edits; it does not block existing users until someone saves them.
- The identifier is the stable part: renaming the display name is safe, renaming the identifier is not, because rules that reference it stop matching.
Permissions¶
This page requires PM_USERS. See
Permission reference.