home.md

@@ -29,6 +29,7 @@ To do that, you have to export your project from the other GitLab instance and i
 **Important notice**: before doing the import, make sure that all the user accounts referenced from the project in the previous GitLab instance are re-created identically in this GitLab instance **before** importing the project. This is not mandatory for the git history data, where the commiter is just a string, but it is mandatory for all GitLab specific tools such as issues, comments, etc. Some of the records for which no corresponding user account are found during import will be attributed the the account which performed the import instead, and some of these records will simply disappear (eg. issues raised or belonging to an nonexistent account simply disappear). Do not forget that for Inria members, for their accounts to be activated in GitLab, they need to login at least once to GitLab.
 
 # limitations:
+* any users that did not connect during 90 days will have their account automatically deactivated. One can reactivate the account with a simple [new connection](https://gitlab.inria.fr/users/sign_in). If your account is deactivated and have lost your password you have to directly [contact administrators](https://helpdesk.inria.fr/) because the email password reset is not working in this context.
 * users can create up to 50 projects
 * project size are limited to 2GB
 * GitLab's integrated continuous integration is enabled by default on all projects, but we do not currently provide support for this. More specifically we do not yet provide support for interfacing GitLab with Inria's continuous integration platform.
\ No newline at end of file