translated by Google

Machine-translated page for increased accessibility for English questioners.

GitLab FI


The custom grouping feature is turned off in GitLab to prevent collisions with synced groups. If you need to create your own group or want to enable group synchronization, contact your administrator.

GitLab will send you an email if you become a member of any group.

Synchronization with faculty administration

This setting is useful for manually managed groups in faculty administration, such as research groups, faculty departments, or conferences.

When synchronization is in progress

Administrators and group members are synchronized every hour . For newly created accounts (after the first login to GitLab), partial synchronization will start immediately.

Members' rights

For the Owner right, synchronization tries to be as consistent as possible with the faculty group settings:

  • If the faculty group has at least one administrator , then the Owner right is automatically kept consistent with the list of administrators. If someone grants the Owner to other members, they will lose this right the next time they sync.
  • If the faculty group has no administrator , then the Owner right is not synchronized. The administrator may grant this right to other members.

Other members of the group are given the default right when synchronizing (this can be specified when requesting synchronization settings). These rights can be changed by the group administrator in GitLab to any value other than Owner .

An impersonal Root account is also a member of such a group, so that large changes in subject groups (usually between semesters) do not cause the group to lose all administrators. This account ignores notifications, so it doesn't make sense to tag it.

Management group

For the purpose of better organization of faculty groups, it is also possible to request the creation of a management group , usually with a prefix adm_ which has the following characteristics:

adm_X can manage members adm_X (ie self)
Administrators can grant administrative rights to other members by adding them to an administrative group.
adm_X manages group_X (or mail_X ,…)
Administrators can add more members to managed groups.
adm_X is a subgroup group_X (or mail_X ,…)
Administrators can automatically be members of a group.
This setting is recommended but not required.

Sync settings request

Write to . In your request to form a group, provide at least the following information:

  • The name of the faculty group you want to sync. If necessary, we can create a group, then provide information about this group.
  • If the group does not have an administrator in the faculty administration , state the initial owner of the group.
  • Default permissions that new group members will get in GitLab. You can then change this right for specific members in the group settings in GitLab.

read instructions for GitLab group administrators !

Synchronization with IS MU

Synchronization can also be set for synchronization of groups in IS. It is typically used to synchronize the list of students or subject teachers in the current semester with a group in GitLab.

Due to technical limitations, accounts cannot be synchronized directly from the IS to GitLab, so faculty groups are used as a synchronization interface:

  1. Every two hours , teachers or students synchronize to a faculty group.
  2. Every hour , the members of the group synchronize with GitLab in the same way as described above.

This part of the documentation therefore describes the possibilities of synchronization between the IS and the faculty groups. The synchronization of the faculty group with GitLab then takes place according to the documentation above.

Manually add members

Additional members can be added manually to synchronized faculty groups from the IS. This is useful, for example, for making GitLab materials available to external consultants, older students, etc.

However, be careful that these people will never automatically cancel the synchronization with the IS from the group.


Because both students, teachers, and both can be synchronized from the IS, synchronization can be set up in various ways.

Group for students only

Suitable for allowing access to shared materials or for subject projects.

For proper functioning, it is necessary to designate administrators in the group, which are usually teachers or members of the laboratory. If you do not want to maintain the administrator manually, we recommend that you use the Student and Teacher Group configuration.

Group for teachers only

In this configuration, the members of the group are only teachers. Upon request, it is possible to specify whether it is a lecturer , instructor , assistant , or any combination of these subject roles.

Group management can be granted to individual users or to another group. We can also create an automatically synchronized management group for subject lecturers only.

Group for teachers and students

This configuration is recommended for synchronizing subjects where teachers and students want to have access to the same repositories, but generally with different rights.

At least three faculty groups are used for synchronization:

  • Management group. This usually includes all teachers. If necessary, it can be divided into a group for lecturers and a group for others.
  • Group for students.
  • A group that contains both of the previous ones. This synchronizes with the GitLab group for the subject. The group for teachers then has the right to administer this group, so they get the right of Owner .

The advantage of this division is also the possibility to set up additional synchronizations, eg for a group of teachers only.

Not sure which configuration to choose?

Write to us at how you want to use groups in GitLab, and we will try to find a suitable setting.


For faculty groups, we can create an e-mail alias on request.

You can also set up synchronization for a subgroup in GitLab. For example, you might have a group in which only members are teachers, and then a subgroup in which students sync. You can then move projects between these groups that you want to make available to students.

Sync settings request

Write to . In your request to form a group, provide at least the following information:

  • Subject code or name of the group in the MU IS that you want to synchronize.
  • If you also want to synchronize teachers, specify which roles the synchronization applies to ( lecturers , teachers , assistants, or combinations).
  • Specify which configuration you require, or describe what rights each role should have.
  • choose default permissions , for each group that the configuration will require.

read instructions for GitLab group administrators !

Manually managed group

If you don't want to use sync, just ask to create a regular group in GitLab FI. Restrictions on synchronized granting groups do not apply here, ie the administrator may give the Owner the right to other members at will.

Write the request to create a group to where you provide the name of the group and the initial administrator.

Instructions for GitLab group administrators

If you have been granted the right of a group owner, GitLab will allow you to change its settings.

  • You can change the Group Name .
  • You can change the description of the group ( Description ).
  • You can change the visibility of the group ( Visibility ) and the projects in it. When you set up synchronization, the group is always created with Private visibility.
    When setting visibility to Public or Internal , first check the project visibility settings. This prevents unwanted publication of projects with sensitive data.
  • Never change the way the group (Path) without the knowledge and consent of the administrators GitLabu!
    Unfortunately, this option cannot be disabled in the settings.