... | ... | @@ -93,6 +93,9 @@ Before leaving Inria: |
|
|
* The administrator open a ticket requesting to convert the account, providing the external email that will be used as identifier and for password recovery.
|
|
|
* the user ask for password recovery using the new identifier when the account has been converted and provide a new password.
|
|
|
|
|
|
## How to convert a user account from external to internal
|
|
|
External users can one day be hired by Inria and ask for an internal gitlab account. In this situation the external account can be converted into an internal one with proper inria email and iLDAP parameters. To do so the user must open a ticket (https://helpdesk.inria.fr/, section gitlab) requesting to convert the existing external account into an internal, providing the current external account login (e.g. x-Jdoe), the inria email and iLDAP login.
|
|
|
|
|
|
## How to activate a commit email hook
|
|
|
|
|
|
Gitlab's model is that instead of setting up a centralized commit email hook per project, it is rather up to the users to choose his/her notification level per project. All users can set their 'global' notification level setting in their account settings. Then they can override this default global notification level per project on top of the project details page, with the little bell (This way, a project cannot impose a notification level to its members).
|
... | ... | |