Text of docs.gitlab.com › user › import › mapping › reassignment as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Reassign contributions and memberships | GitLab Docs

/ Reassign contributions and memberships Users with the Owner role for a top-level group can reassign contributions and memberships from placeholder users to existing active non-bot users. On the destination instance, users with the Owner role for a top-level group can: Request users to review reassignment of contributions and memberships in the UI or through a CSV file . For a large number of placeholder users, you should use a CSV file.

In both cases, users receive a request by email to accept or reject the reassignment. The reassignment starts only after the selected user accepts the reassignment request . Choose not to reassign contributions and memberships and keep them assigned to placeholder users . On GitLab Self-Managed and GitLab Dedicated, administrators can reassign contributions and memberships to active and inactive non-bot users immediately without their confirmation.

For more information, see skip confirmation when administrators reassign placeholder users . To reassign contributions and memberships to administrators, see allow contribution mapping to administrators . Bypass confirmation when reassigning placeholder users Tier : Premium, Ultimate Offering : GitLab.com Introduced on GitLab.com in GitLab 18.1 with a feature flag named group_owner_placeholder_confirmation_bypass . Disabled by default.

Enabled on GitLab.com in GitLab 18.4. Generally available on GitLab.com in GitLab 18.7. Feature flag group_owner_placeholder_confirmation_bypass removed. Prerequisites: You must have the Owner role for the group. To bypass confirmation for enterprise users when you reassign placeholders: In the top bar, select Search or go to and find your group. This group must be at the top level. In the left sidebar, select Settings > General .

Expand Permissions and group features . Under Placeholder user confirmation , select the Reassign placeholders to enterprise users without user confirmation checkbox. In When to restore user confirmation , select an end date for bypassing user confirmation. The default value is one day. Select Save changes . Reassigning contributions from multiple placeholder users You can reassign all contributions initially assigned to a single placeholder user to a single active regular user, service accounts, project bots, and group bots on the destination instance.

You cannot split contributions assigned to a single placeholder user among multiple users. You can reassign contributions from multiple placeholder users to the same user on the destination instance if the placeholder users are from: Different source instances The same source instance and are imported to different top-level groups on the destination instance If an assigned user becomes inactive before accepting the reassignment request, the pending reassignment remains linked to the user until they accept it.

Users that receive a reassignment request can: Accept the request . All contributions and membership previously attributed to the placeholder user are re-attributed to the accepting user. This process can take a few minutes, depending on the number of contributions. Reject the request or report it as spam. This option is available in the reassignment request email. When you reassign contributions to service accounts, project bots, and group bots, the reassignment request is automatically approved.

In subsequent imports to the same top-level group, contributions and memberships that belong to the same source user are mapped automatically to the user who previously accepted reassignments for that source user. On GitLab Self-Managed and GitLab Dedicated, administrators can reassign contributions and memberships to active and inactive non-bot users immediately without their confirmation. For more information, see skip confirmation when administrators reassign placeholder users .

To reassign contributions and memberships to administrators, see allow contribution mapping to administrators . Completing the reassignment The reassignment process must be fully completed before you: Move an imported group in the same GitLab instance . Move an imported project to a different group . Duplicate an imported issue. Promote an imported issue to an epic. If the process isn’t complete, contributions still assigned to placeholder users cannot be reassigned to real users and they stay associated with placeholder users.

Security considerations Reassignment of past contributions and memberships is permanent and cannot be undone, so check everything carefully before you start. Users can revoke an accepted reassignment , but revocation only prevents automatic reassignment in future imports. Reassigning contributions and membership to an incorrect user poses a security threat, because the user becomes a member of your group. They can, therefore, view information they should not be able to see.

Reassigning contributions to users with administrator access is disabled by default, but you can enable it. Membership security considerations Because of the GitLab permissions model, when a group or project is imported into an existing parent group, members of the parent group are granted inherited membership of the imported group or project. Selecting a user for contribution and membership reassignment who already has an existing inherited membership of the imported group or project can affect how memberships are reassigned to them.

GitLab does not allow a membership in a child project or group to have a lower role than an inherited membership. If an imported membership for an assigned user has a lower role than their existing inherited membership, the imported membership is not reassigned to the user. This results in their membership for the imported group or project being higher than it was on the source. Request reassignment in UI Prerequisites: You must have the Owner role for the group.

You can reassign contributions and memberships in the top-level group. To request reassignment of contributions and memberships: In the top bar, select Search or go to and find your group. This group must be at the top level. In the left sidebar, select Manage > Members . Select the Placeholders tab. Go to Awaiting reassignment sub-tab, where placeholders are listed in a table. For each placeholder, review information in table columns Placeholder user and Source .

In the Reassign placeholder to column, select a user from the dropdown list. Select Reassign . Contributions of only one placeholder user can be reassigned to an active non-bot user on the destination instance. Before a user accepts the reassignment, you can cancel the request . On GitLab Self-Managed and GitLab Dedicated, administrators can reassign contributions and memberships to active and inactive non-bot users immediately without their confirmation.

For more information, see skip confirmation when administrators reassign placeholder users . To reassign contributions and memberships to administrators, see allow contribution mapping to administrators . Request reassignment by using a CSV file Introduced in GitLab 17.10 with a feature flag named importer_user_mapping_reassignment_csv . Enabled by default. Generally available in GitLab 18.0. Feature flag importer_user_mapping_reassignment_csv removed.

Prerequisites: You must have the Owner role for the group. For a large number of placeholder users, you might want to reassign contributions and memberships by using a CSV file. You can download a prefilled CSV template with the following information. For example: Source host Import type Source user identifier Source user name Source username gitlab.example.com gitlab alice Alice Coder a.coder Do not update Source host , Import type , or Source user identifier .

This information locates the corresponding database record after you’ve uploaded the completed CSV file. Source user name and Source username identify the source user and are not used after you’ve uploaded the CSV file. You do not have to update every row of the CSV file. Only rows

The rest of this page is on the live site.