This form contains information on the user, some of which is common to that of the corresponding agent.
For rules on how to use the fields, see Detail form.
- User (required): Identifier of the user. You may, if desired, choose an identifier that will be used as an access code (or login), as offered by default by the application.
- Standard: If checked, the user is considered as Standard.
- Status: User status.
Contact details
- Agent: Code of the corresponding agent; see Creating an agent. It is not possible to associate several users with the same agent.
- Name, contact details, external, main location: these are identical for the agent and user.
Context
- Language, time zone, currency, calendar: these are identical for the agent and user.
Connection
- Username: The access code that the user enters to log in. Initialized with the user code; you can change it to replace it with the email address or another code.
- Password and confirmation: The password to be entered by the user when connecting; see Administering users.
- Validity duration and end: Indicates the time after which the user must change their password. The duration is in days.
- Reinitialize: To be checked if the user has to change their password upon the next connection.
The password management policy is specified in the System configuration. the following settings are found in that file:
- minPasswordSize: minimum size of the password,
- nbConnectionTries: number of connection attempts before the account is locked,
- passwordHistoryValidity: history of the number of passwords.
Configuration
- Business vocabulary: Indicates the user's vocabulary; if there are business-context-specific customized terms; see Customization of names.
- Profile: Required for access to CARL Source functions; see Profile.
- Organization group: Restricts access to data depending on the organization; see Organization group.
- Restriction group: Restricts data access according to technical criterion; see Access restriction.
- Customization group: Customization group to which the user belongs. If not defined, the user will only see the standard forms.
- Map group: Restricts access to data depending on a map criterion; see Map groups.
Role
- Organization: Organization to which the user belongs. The organization is used to restrict access to data if organization groups have been defined.
- WR addressee: To be checked if the user can be indicated as a WR addressee.
- Mobility: Check this box if the user is required to use CARL Touche.
- Technician: Check this box if you would like to create a technician quickly. When this box is checked, the Team (required), Discipline (required) and Time type fields become accessible.
- Customer: Check this box if you would like to create an Customers quickly.
- Tenant: Check this box if you would like to create a tenant quickly.
- Generic account: A generic account will require a double authentication: authentication with CARL Source's internal password, followed by the entering of a token obtained from the BL.auth service.
This is required if, for example, someone from CARL Berger-Levrault support needs to log in to your application using the generic CARLSUPPORT account; double authentication will make it possible to trace the real person.
After saving, you can go directly to the sheets created (technician, customer or tenant).
CONSENT
- Consent type (required): two possible values (Optional or Required). If Optional, the agent is not required to give their consent to the General Terms of Use when connecting. If Required, the agent is required to give their consent when connecting. In this case, they can accept or refuse. This attribute can only be changed on the Agent sheet.
- Withdrawal right (read-only): this checkbox identifies whether an agent has accepted or refused the General Terms of Use.
- Consent date (read-only): Date on which the consent was given.
- Consent agent(read-only): Agent who gives consent.
Consent type is an attribute subject to a profile right (CARL Source/Global/Manage consent). Consequently, if this profile right is not enabled, the administrator cannot change the field value.
While all consent information is managed in the agent, it is visible on the user sheet. The Update consent action is only available from the Agent function, and not from the User.
External account
- BL.Predict account: BL.Predict. platform access account.
To avoid having to enter the BL.Predict account field for each user affected. This setting is also available in the profiles, in the settings associated with the "BL.Predict dashboard configuration" profile right.