Create a User Account.
|Field name||Explanation||Example value|
A username for the user that they will use to sign in or author content items. Spaces are allowed; punctuation is not allowed except for periods, hyphens, apostrophes, and underscores.
A valid email address for the user. All emails from the system will be sent to this address. The email address is not made public.
A password the user will use to sign in to the site. You can see how safe the password is on the Password strength gauge. You also get tips on how to make it safer.
Type the same password to avoid any typing mistakes.
Set the status of the user account. Blocked users will not be able to sign in.
Set the role of the user account.
Notify user of new account
Enable checkbox to send a notification to the user’s email address.
Select the account's preferred language for emails and profile information.
Select the affiliates that this user belongs to. Used to grant editing permissions for users with the "edit domain content" permission.
Gitlab file field default settings
Used to select a default GitLab related account, a project and branch for GitLab type file fields, because every time a user wants to link a GitLab file (for example at Example type nodes) he has to select a GitLab account, a project inside that account and a branch inside the selected project to be able to see the available file list for linking. For example if given an Example type node (where GitLab type file fields available), then when the user opens the node for editing, the account, the project and the branch related fields will be automatically filled according to the user's settings. But when a GitLab file field field has its own default account/project/branch settings, those settings always override the user's settings.
[GitLab account, project, branch]