© CIT

GitLab

Service: If you develop software as part of (research) projects, Gitlab is available for version management. The system offers essential management and bug tracking functions.

Target Group: employees, students

Usage Costs: free of charge

Access: gitlab.git.nrw

Contact: gitnrwsupport@uni-muenster.de

  • Applying for Groups

    Groups in GitLab are very powerful because they come with extensive rights for project and user management. We therefore only create groups upon request. The following conditions apply:

    • GitLab groups are only assigned to an institution or working group that is also part of the University’s organizational structure.
    • There must be a primary contact person (owner) responsible for the GitLab group. The person submitting the request should hold at least a group leadership position (as defined by the University of Münster’s central identity management system), typically the leadership of a working group. 

    Please request groups via gitnrwsupport@uni-muenster.de.

  • Managing Groups

    Security

    Given the extensive access rights you have as the owner of a group, you should definitely enable two-factor authentication for your account. You can do this at gitlab.git.nrw/-/profile/two_factor_auth.

    Access Rights

    How you organize yourself internally within a GitLab group is up to you. As the owner, you must initially assign permissions to other group members. This can be done with a high degree of granularity. You can also add additional owners to share group administration with colleagues.

    Learn more about permissions at gitlab.git.nrw/help/user/permissions.

    Subgroups

    Before creating projects in your group, you should consider the structure of subgroups. It is recommended not to work directly at the top-level group, but rather to plan topic-specific subgroups and create projects within them. This makes it easier to organize and separate memberships, roles, and access rights later on, as permissions are inherited by subordinate groups.