faq.md

@@ -73,21 +73,19 @@ The procedure and detailed information are provided [here](https://doc-si.inria.
 
 ## How to convert a user account from internal to external
 
-When a user is leaving Inria, the gitlab account cannot be used anymore.
+When a user is leaving Inria, the gitlab account cannot be used anymore. To keep the access to the project, please follow this procedure, before or after the user has left.
 
-Anyone with an active Inria account can open a ticket on helpdesk.inria.fr in the category "Demande sur GitLab", requesting to convert the account, providing :
+Anyone with an active Inria account can open a ticket on helpdesk.inria.fr in the category "Demande sur GitLab", requesting to convert the account and providing :
 
 * the name/firstname/login of the person leaving Inria,
 * the external email that will be used as identifier and for password recovery,
 * the name of the sponsor at Inria and
-* until when the account is needed (maximum is 3 years).
+* until when the account is needed (maximum is 3 years, renewable by the sponsor).
 
-The conversion will not be made before the user has left Inria :
+The conversion will be made after the user has left Inria, when the Inria account is deactivated (which occurs when the Human Resources service closes the Inria account, between 1 and 3 months after the departure):
 
-* the new account will be available when the Inria account is deactivated, which occurs when the Human Resources service closes the Inria account.
-* then, when the account has been converted, the user can ask for password recovery using the new identifier and provide a new password.
-
-(For Mattermost, there is no other way than deleting the internal access before adding the new account to each Mattermost team.)
+* an administrator mades the conversion to the new account and gives the new identifier to the user;
+* then, the user can ask for password recovery using this new identifier and provide a new password.
 
 ## How to convert a user account from external to internal