@@ -24,6 +24,17 @@ There are some conventions associated with robot account users:
* They must have a valid role email address associated with them. An initial password reset token is emailed to this address when created.
* We recommend that the robot user is configured with [2FA enabled](https://docs.gitlab.com/ee/user/profile/account/two_factor_authentication.html). This helps guard against some of the dangers of having an account with shared access credentials.
## How can I get an additional administrator account?
Administrators of institution-wide groups may wish not to use their day-to-day account for group-wide administration because they feel they have too much incidental visibility within the group. For top-level group owners, we're willing to give out additional administrator accounts.
There are some conventions associated with administrator accounts:
* They are tied to a single named user.
* 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``.
* 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).
## How can I invite external collaborators?
An "external collaborator" is someone who you wish to give access to a Developer Hub project but who does not have an active Raven account. We grant external collaborator accounts on a case-by-case basis. [Open an issue in this project](https://gitlab.developers.cam.ac.uk/uis/devops/devhub/docs/issues/new) if you want an external collaborator account created.
