home.md

@@ -6,7 +6,7 @@ Inria's GitLab service address is https://gitlab.inria.fr
 
 # GitLab accounts
 * All users with an Inria ldap account have immediate access to this GitLab with their Inria account, by login in the **iLDAP** login tab. They have standard GitLab permissions: create projects, groups, and administer them. 
-* All users without an Inria account can [create an account](https://gitlab-account.inria.fr/). They will receive a confirmation mail, and after their account is confirmed, they get an [external account](https://gitlab.inria.fr/help/user/permissions.md#external-users). Then they can login in the **Standard** login tab. They won't be able to create projects nor groups, but can be invited by Inria members to participate in project(s).
+* All users without an Inria account can request an account from an INRIA member with which they collaborate. INRIA members can create accounts for external users on the [external account management portal](https://external-account.inria.fr/). They will receive a confirmation mail, and after their account is confirmed, they get an [external account](https://gitlab.inria.fr/help/user/permissions.md#external-users). Then they can login in the **Standard** login tab. They won't be able to create projects nor groups, but can be invited by Inria members to participate in project(s).
 This logic is similar to the [InriaForge](gforge.inria.fr)'logic regarding permissions of Inria members versus external users, the difference being that the InriaForge accounts database is separated from the Inria ldap accounts database, whereas GitLab supports dual authentication (ldap or external).
 
 Note that for Inria members, the corresponding GitLab account is activated upon the first connection. So, to activate your accounts and allow projects or group administrators to add you to projects or groups, you need to login to the GitLab at least once.