'User'
(User)

Active

active

$true (Boolean)

The Active checkbox must be ticked so that a user account can be used for a User login.

Username

username

'don.duck@doma.in'
'don.duck@nasa.gov'
'manon.moon@nasa.gov'
'moon69'
'MoM'
'mom'

A system-wide unique character string (case-sensitive) must be entered as the Username.

►NOTE◄ The uniqueness of the Username is only verified when saving. Saving is cancelled with an error message if the specified user name has already been assigned.

As each user account can be identified as an entity via a unique ‘ID’ (id), the Username can be changed again for users that have already been created. However, this is only recommended to a limited degree, as the Username can also be used as a reference in the context of Orchestration integration (e.g. via Integration login or Create Login Request (Integration function)). Such references may be orphaned after being renamed.

Password

Password confirmation

(passwordHash)

'69f50cde6DD6'

See also:

Change password
Password guidelines
'Forgot password' function

When creating a user, a Password must be entered and repeated without errors in the Password confirmation field.

• The display of characters during input is hidden (*******).

• No characters are displayed for users who have already been saved.

• If both fields are empty when saving, an existing password is retained.

• If both fields contain matching entries when saving, the input overwrites an existing password without this having to be entered.

Password expiry date

passwordExpiryDate

22.05.2025 22:00(UTC)(DateTime)

A Password expiry date can optionally be specified to trigger a prompt to change the password if the expiry date has already been exceeded when attempting to log in (with the previously valid password).

►IMPORTANT◄ If a new password is entered in this dialogue and repeated correctly, this triggers the ‘Change’ event (see Common action event) for the user account. Event handling, which reacts to the ‘Change’ event for Users (see Check type), can evaluate two Boolean variables in this case:

• The Variable passwordTouched returns the value $true if the dialogue has been opened and a password has been entered and confirmed.

• The Variable passwordChanged returns the value $true if the confirmed password is actually different from the previous one.

The Password expiry date for the user is then already deleted. If a Password expiry date should also apply to the new password, this must be determined explicitly and assigned to the passwordExpiryDate field. With the Relative date with time resolver, this is possible either based on the current system time or, if applicable, relative to the previous expiry date, which can be read in the context of the ‘Change’ event via the Original entity resolver.

Locale

locale

'English' (en)

Simple selection that links a specific Sprache to the company.

Max. concurrent sessions

maxConcurrentSessions

1

This setting determines how many Lobster Data Platform sessions a user may use simultaneously. This restriction is checked at each login attempt. If a user exceeds the personal limit with an additional session, the new session will only be activated if the user agrees to log out of an existing session:

Companies

companies

'SL UK', 'SL Germany',
'Hidden company account'

Multiple selection of Companies/Clients from which the user can select the Company of session when logging in. If precisely one company is selected here, the company selection at login is omitted.

►NOTE◄ The label ‘Hidden company account’ appears for companies that are already assigned and can therefore be removed in the context of the current session but cannot be selected again afterwards.

►IMPORTANT◄ A user account that refers to a 'Hidden company account' can be changed but not created. This is particularly relevant when copying an existing user account. If necessary, all hidden companies must be removed so that the copied user account can be saved.

To access Companies/Clients for a Company selection for Users, the following scenarios must be defined by default:

• The Company of session and Companies/Clients that it owns can always be selected.
  
  

• Other Companies/Clients can only be selected as Companies for Users in the context of Roles that take owner restrictions into account if they grant the Company of session permission to 'Change' or 'Create' their Users via Company authorizations. Authorisation to ‘Change’ affects the company selection in user accounts that have already been saved. The ‘Create’ authorisation affects the company selection for newly created or copied user accounts that have not yet been saved. It should be noted that these authorisations are also required to link the issuing company to a user account that the Company of session itself has or should have. However, no read access needs to be enabled for the Users of the issuing company affected by the authorisation. The granting company itself does not need to have read access either.

In custom Input forms for Users, access in these two cases can be restricted by specific search restrictions for the Combobox element.

Roles

roles

'Guest', 'Admin (accounts)',
'Hidden role'

Multiple selection for Roles from which the user can select the Role of session when logging in. If precisely one role is selected here, the role selection at login is omitted.

►NOTE◄ The ‘Hidden role’ label appears for roles that are already assigned and can therefore be removed in the context of the current session but cannot be selected again afterwards. This applies to all Roles that cannot be accessed with the Role of session.

►IMPORTANT◄ A user account that relates to a ‘Hidden role’ can be changed but not created. This is particularly relevant when copying an existing user account. If necessary, all hidden roles must be removed so that the copied user account can be saved.

'Addresses'
(Address)
see Adressen

Salutation

address.salutation 

'Mr' (MR)

Single selection for the Anrede in the user address.

Name

address.name1

'Don'

Free text that is used together with other fields for labelling.

Name 2

address.name2

'Duck'

Free text that is used together with other fields for labelling.
►NOTE◄ If required, the 'Name 3' (address.name3) field is also available.

Street

address.street1 

'Entenwerder Stieg'

Free text for the street in the postal address.
►NOTE◄ If required, the ‘Street 2’ (address.street2) field is also available.

Street no.

address.streetNo

'66'

Free text for house number(s) in the postal address.

Account-No.

address.accNumber

'1901'

Free text that can be used, for example, to specify an identifier for the user account in other systems.

Country*

address.countryCode

'Germany' (DE)

Single selection for the Land in the postal address.

Zip code*

address.zipcode

'20359'

Free text for the Zip code in the postal address.

City*

address.city

'Hamburg'

Free text for the name of the city in the postal address.