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 a default right when syncing (this can be specified when requesting sync 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 there is no point in tagging 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 myself)
Administrators can grant management rights to other members by adding them to the management 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 necessary.

Sync settings request

Write to . In the request for group formation, provide at least the following information:

  • The name of the faculty group you want to synchronize. 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 members of the group 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 IS to GitLab, so faculty groups are used as an intermediate step of synchronization:

  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 adding 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 also 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 laboratory members. If you do not want to maintain the administrator manually, we recommend that you use the Student and Teacher Group configuration.

Teachers only group

In this configuration, group members are only teachers. Upon request, it can be specified whether it is a lecturer , instructor , assistant , or any combination of these subject roles.

Group management can be granted for individual users or 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 both 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 only teachers.

Not sure which configuration to choose?

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


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

Synchronization can also be set 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.

If you are requesting the creation of a group for a research group, consider having students which projects are important to your group. It is then advisable to move such projects to this group ( SettingsGeneralAdvancedTransfer project ) so that you do not lose them at the end of your studies and do not have to deal with it unnecessarily complicated.

Sync settings request

Write to . In the request for group formation, provide at least the following information:

  • Subject code or group name in IS MU that you want to synchronize.
  • If you also want to synchronize the teachers, specify which roles the synchronization applies to ( lecturers , teachers , assistants or combinations).
  • Specify what 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 do not want to use synchronization, just request the creation of an ordinary group in GitLab FI. Restriction restrictions for synchronized groups do not apply here, ie the administrator can give the Owner the right to other members as desired.

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

Instructions for GitLab group administrators

If you have been granted group ownership, GitLab will allow you to change its settings.

  • You can change the Group Name .
  • You can change the description of the group .
  • 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 will prevent you from accidentally publishing projects with sensitive data.
  • Under no circumstances change the path to the group without the knowledge and consent of the GitLab administrators!
    Unfortunately, this option cannot be disabled in the settings.