Deprovisioning Policy
The deprovisioning policy for the "GitLab at KIT" service specifies the procedure for handling stored Git repository data belonging to users after they stop using the service.
Registration
The GitLab service is provided under the following conditions:
-
An active user account exists in the KIT user management system.
-
An external user account is authenticated by the identity provider of the user’s home institution and identified at KIT via the federated login system (FeLS).
-
The user has registered for GitLab at KIT during their initial login.
These criteria are verified via identity management in bwIDM. For the GitLab service user accounts are maintained within KIT’s user management system.
Deprovisioning
GitLab accounts are deprovisioned by deregistering a user account in FeLS. The process is initiated for two main reasons:
-
The user account in the home institution’s local user management system is no longer active.
-
The user has unsubscribed from the service themselves on the registration page (https://bwidm.scc.kit.edu).
The deregistration of a GitLab account at KIT takes place 3 months after the user account has been deactivated in the local user management system (bwIdM). Immediately after a local user account is deactivated, an email from “git@scc.kit.edu” is sent to the registered primary email address, informing the user that the user’s account must be renewed in their local account management system and that the GitLab account has been deactivated. Inquiries regarding local user accounts must be addressed by your organization’s account management department. If the user account is reactivated by the responsible department at the user’s home institution, the user can log in to the GitLab service again. If the user previously chose to have their account removed from the service, this action can be reversed by re-registering. Once an account has been deregistered, it is no longer possible to log in to the GitLab service.

Permanent Deletion of GitLab Accounts
365 days after deregistration, both the GitLab user account and any associated projects and data belonging to the deregistered user are handled differently depending on the account type:
-
KIT Member, Guest & Partner Accounts:
If the GitLab user has NO other memberships in other GitLab projects and groups and has NOT contributed to shared projects and groups, the GitLab account will be deleted; otherwise, the GitLab account will remain active and will not be deleted.
-
Student Account:
365 days after deregistration, both the GitLab user account and any associated projects and data will be deleted. Before deletion, the user’s personal projects will be archived, and ownership of any shared groups and associated projects held by the deactivated user will be transferred to the other owner or a GitLab administrator.
-
External Account:
External accounts do not have their own storage space in GitLab. If the GitLab user has NOT contributed anything to projects or groups, the GitLab account will be deleted; otherwise, the GitLab account will remain active and will not be deleted.