@@ -32,7 +32,7 @@ There are some conventions associated with administrator accounts:
...
@@ -32,7 +32,7 @@ There are some conventions associated with administrator accounts:
* They are tied to a single named user.
* They are tied to a single named user.
* They are named ``{group}-admin-{crsid}``. For example: ``uis-admin-spqr2``.
* They are named ``{group}-admin-{crsid}``. For example: ``uis-admin-spqr2``.
* They must have a valid email address associated with them which is not of the form ``{crsid}@cam.ac.uk``. We would recommend either a institutional address or the use of sub-addressing. For example: ``{crsid}+gitlab-{group}-admin@cam.ac.uk``.
* They must have a valid email address associated with them which is not of the form ``{crsid}@cam.ac.uk``. We would recommend either a institutional address or the use of sub-addressing. For example: ``{crsid}+gitlab-{group}-admin@cam.ac.uk``.
* As an account intended for group-wide administration, we recommend that the user is configured with [2FA enabled](https://docs.gitlab.com/ee/user/profile/account/two_factor_authentication.html).
* As an account intended for group-wide administration, we recommend that the user is configured with [2FA enabled](https://docs.gitlab.com/ee/user/profile/account/two_factor_authentication.html).
* GitLab admins may opt to disable the account if the named user associated with the account ceases to administer the related group.
* GitLab admins may opt to disable the account if the named user associated with the account ceases to administer the related group.