1. You are here:
2. Handbook
3. People Group
4. GitLab Offboarding
5. GitLab Offboarding Guidelines

Maintained by:

On this page

• Offboarding Issues
  • Creating the offboarding issue
• BambooHR
• Tools Offboarding
  • G Suite
  • Slack
  • Team Page
• Compliance

The People Experience Associate in the relevant rotation will assign the offboarding team member to a People Experience Associate from within the offboarding tracker. Once assigned, the assigned People Experience Associate creates the offboarding issue, within 12 hours of the offboarding date (may be sooner once the relevant Associate in the rotation is online) as is stipulated in the #offboarding Slack channel submitted by the People Business Partner. Many other teams work to deprovision access including the ITOps team, this should be regarded as urgent and expected to be completed in 5 working days with the exception of Laptop returns, which can take 2 - 4 weeks.

Offboarding Issues

To ensure a successful completion of the offboarding issue and compliance, it is important that all tasks are checked off, whether the system/tool is applicable to the offboarding team member or not. Checking the box indicates one of the following:

• I have revoked team member access to this particular system/tool
• I have checked and this team member was not given access to this particular the system/tool

Creating the offboarding issue

1. In Slack, go to your profile as if you were going to send a Slack message to yourself. Type the command /pops run offboarding BambooHR_ID_number (not Employee ID #). This number is found in the team member's BambooHR profile URL, after id=. It is a 5-digit number. An example of the command would be /pops run offboarding 00000. If BambooHR's API is down, this ChatOps command will fail and will need to be created manually.
2. You will be pinged in Slack once the offboarding issue is created, which usually takes 30 seconds or so. The ping will include a link to the new offboarding issue.
3. You will need to update the Department, GitLab Email Address and GitLab Handle within the issue.

Note: If the team member is transitioning to a temporarily positioned contractor, please proceed with the full offboarding and create a separate onboarding issue to grant only specific temporary access for what they would need to fulfill their contractual obligations.

BambooHR

1. Update Employment Status -
   1. Effective Date
   2. Employment Status
   3. Termination Type
   4. Termination Reason - Ensure the PBP gives you a reason listed within BambooHR.
   5. Eligible for Rehire
2. Then click on the setting gear symbol in the right hand corner and set employee to terminated
3. If the team member is within their probation period, delete the "End of Probation Period" and "Active" entries. The top entry in the Employment Status table should be the "Termination" entry.

If the team member is on the People Team, the People Experience Associate will need to notify the Total Rewards team in order to have them update the employment status.

Tools Offboarding

G Suite

IT Ops will follow the below steps to set up an auto-response that notifies the sender that the team member they are trying to reach is no longer with GitLab and who to contact.

1. Add the team member to the former_employees@gitlab.com's email account by selecting the dropdown icon ˇ in the User information section and adding the team member's GitLab email address.

Note: Be sure to scroll down and Save this change or it will not be reflected.

1. Set up a routing rejection rule for the team member by;
   1. Navigate to Google admin portal then Apps > G Suite > Gmail > Advanced settings > Routing > Routing.
   2. Hover over the routing option and click on Add another. Please enter a name below the title "Routing" with lastname firstname rejection rule
   3. Check the option Inbound and Internal-receiving under Messages to affect.
   4. Check Only affect specific envelope recipients under the Envelope filter title.
   5. Enter the team members's email address right below the title Email address.
   6. Under the title For the above types of messages, do the following, please change from Modify message to Reject message.
   7. Add the appropriate template per team member's department under the Customize rejection notice
   8. Scroll down and click on Add setting and then on Save at the bottom (once the window closes).

After 5 days, when the former team member's offboarding issue is due, IT Ops will delete their GSuite account now refered to as former_username@gitlab.com. During this process, you will receive a prompt to transfer their Google Drive Documents. Please refer to the offboarded team member's Offboarding issue to review if the manager has requested to have Document ownership already transferred to them, or if they have agreed to not receive ownership.

Slack

IT Ops check if the team member has created any bots before disabling the account. Go to Slack or on your admin Slack profile click Menu » Configure Apps » Custom Integrations » Bots and search through the bots' list for the team member. If a bot exists, please DM the manager to confirm if the bot should be removed.

Team Page

The People Experience Associate will navigate to the team.yml file. Using Web IDE or your editor of choice, search the team member name and delete their team page image and replace with ../gitlab-logo-extra-whitespace.png. Don't forget to delete the image by navigating to sites/marketing/source/images/team while still here and search for their image. Ideally saved as firstnamelastname.png. The images are in alphabetical order.

To remove pet entry and any mentions from the handbook and documention, you will need to download the www-gitlab-com project to your computer and use a prefered text editor.

To download;

1. Navigate to the Gitlab.com project
2. On the far right corner, click Clone and copy the clone with SSH URL, git@gitlab.com:gitlab-com/www-gitlab-com.git
3. On your command line, run git clone git@gitlab.com:gitlab-com/www-gitlab-com.git This downloads the project to your computer mostly on the document folder. Consider going through the Clone a repository and the Command Line documents to understand further.

To Find All using Atom;

1. Download Atom at atom.io
2. After installing, click Open Project on the Welcome Guide Page.
3. Choose www-gitlab-com project from your Documents folder
4. On the Find tab drop down menu, click Find in Project
5. Search all variations of the departing team members name; firstname, lastname and GitLab username.
6. Follow the File path given in the results on the Web IDE and delete all the mentions, make sure to replace any mentions you deem appropriate with who is standing in for the position. DO NOT delete any blog mentions.

Compliance

The People Experience Associates in the relevant rotation will complete a weekly audit of all offboarding issues opened within that specific week and check that all tasks have been completed by all Team Member and/or Departments. In the event that tasks are still outstanding, the People Experience Associate will ping the relevant Departments within the offboarding issue to call for tasks to be completed.

Once all tasks have been completed, the People Experience Associate will close the offboarding issue and mark as completed in the offboarding tracker.

All offboarding tasks by all Departments need to be completed within 5 days of the offboarding date. For systems that are more critical and time sensitive, these will be completed within the first 24 hours (example 1Password, Okta, Slack) by the relevant Departments. Information about application & system deprovisioners can be found on the Tech Stack Applications handbook page.