...
Info |
---|
Default Behaviour(s) : By clicking on their user name and avatar in the main DAM Menu, users can update their profile, and more precisely the following information :
Role is displayed as readonly |
Advanced Configuration
Disabling the user profile
Edit the file features/edit-profile.json
with false
.
Modifying user profile
User profile behaviour and display is set in the file profile.json
at the root of the configuration folder.
Disabling avatar modification :
Edit the property avatar.userCanEdit
of the file profile.json
with false
.
Modifying avatar’s subtitle :
Edit (or create) the property displayNameFields
with the desire value. As displayNameFields
is an array, you can put several values that will be concatenated. Possible values ara firstname
, lastname
, email
, name
. Note that this value is defaulted to name
, therefore if you don’t want to display avatar’s subtitle you should put an unknown value like displayNameField: ["none"]
.
Disabling password changes :
Edit the property canEditPassword
of the file profile.json
with false
.
Make field editable or readonly => ⚠ a vérifier si cette config est vraiment dans le portal et pas dans le serveur
To complete
Adding/Deleting a field => ⚠ a vérifier si cette config est vraiment dans le portal et pas dans le serveur
To complete .
Redirection after password change :
Change where the user should be redirected after password change by editing the value of redirectAfterPasswordReset
property of the profile.json
file. You must use a known path (like dam
).
Handle form fields :
You can decide which fields are shown an their order. For most of them you can configure if they are readonly or editable.
To change the displayed fields you should edit the editableFields
of the profile.json
file.
Available fields are : firstname
, lastname
, email
, role
, bolang
.
editableFields
is an array, you can put value inside it as string for simple field configuration or object for more precise field configuration.
If you pass a string, the field will be of type text and editable by default. If you pass an object you can configure the type of the field and its readonly
property.
Putting : { field: "email", type: "email, readonly: true }
will create an input of type email and disallow the user to change its email.
Note that the readonly
property of the role
field is not configured but on the server.
To remove a field from the display you’ll have to remove it from the configuration.