GitLab's annual major release is around the corner. Along with a lot of new and exciting features, there will be a few breaking changes. Learn more here.

Commit 914c75db authored by Lis Vinueza's avatar Lis Vinueza 🌸
Browse files

Rename department

parent 24a4bbc1
Pipeline #272770307 passed with stage
in 7 minutes and 51 seconds
......@@ -49,7 +49,7 @@ In the interests of paying it forward and contributing to our core values of Col
1. [ ] Please inform MktgOps/Outreach provisioners in the access request if the team member is an Outreach user. Any changes to roles in SFDC must be remapped in Outreach.
1. [ ] Coordinate with IT Ops to change any shared passwords, with the intent to be gated behind Okta when possible, in particular;
1. [ ] Review if the team member has sysadmin access passwords for GitLab.com Infrastructure (ssh, chef user/key, others). Identify if any can be moved to Okta.
1. [ ] Review what 1Password vaults team member had access to, and identify any shared passwords to be changed and moved to Okta. If the team member has access to any shared passwords that will no longer be relevant to their new role, please ping `@gitlab-com/business-ops/team-member-enablement` and coordinate shared account password rotation.
1. [ ] Review what 1Password vaults team member had access to, and identify any shared passwords to be changed and moved to Okta. If the team member has access to any shared passwords that will no longer be relevant to their new role, please ping `@gitlab-com/business-technology/team-member-enablement` and coordinate shared account password rotation.
1. [ ] Previous Reporting Manager: If they will become or will no longer be a provisioner of a tool, open an issue to [Update the Tech Stack Provisioner.](https://gitlab.com/gitlab-com/team-member-epics/access-requests/issues/new?issuable_template=Update_Tech_Stack_Provisioner) Please cc the new manager.
1. [ ] Previous Reporting Manager: Arrange a 2:1 handover session with the New Reporting Manager and transitioning Team Member. It is recommended (but not required) to complete the [Career Mobility Handover Template](https://docs.google.com/document/d/1iRbmS518CDjmhZEjvkaibqR1g0angWE83sWvtlH-elE/edit#heading=h.a3i4gy6pj4y7) outlining the team members strengths and accomplishments, goals, and improvement areas. Documenting this information is an important part of the process to commemorate the team member's role transition. 360 feedback may also be reviewed/discussed in this session. _Note: The handover can also take place [asynchronously](/handbook/communication/#asynchronous-communication) if preferred._
1. [ ] Previous Reporting Manager: Review whether [a probationary period is included in the location of the team member](https://about.gitlab.com/handbook/people-group/contracts-and-international-expansion/#probation-periods-of-team-members-employed-through-a-peo) and whether it has ended or is still running. If still running ensure to handover any considerations for the probationary period to the New reporting manager.
......@@ -70,7 +70,7 @@ In the interests of paying it forward and contributing to our core values of Col
1. [ ] Manager: Schedule weekly [1:1 meetings](https://about.gitlab.com/handbook/leadership/1-1/) with new team member. Use the first 15 minutes to get to know your new team member on a personal level.
1. [ ] Manager: Check this box in acknowledgment that the Previous Reporting Manager has scheduled a 2:1 handover session with the new team member.
1. [ ] Manager: Set new GitLab team members' project-level permissions as-needed.
1. [ ] Manager: Add the new team member to the required groups in 1Password if you have access to the Admin Console in 1Password. If you do not have access please ping @gitlab-com/business-ops/team-member-enablement with which vaults the new team member should be added to. Note: if it is necessary to add an individual to a vault (instead of to a group), make sure that the permissions are set to _not allow_ exporting items.
1. [ ] Manager: Add the new team member to the required groups in 1Password if you have access to the Admin Console in 1Password. If you do not have access please ping @gitlab-com/business-technology/team-member-enablement with which vaults the new team member should be added to. Note: if it is necessary to add an individual to a vault (instead of to a group), make sure that the permissions are set to _not allow_ exporting items.
1. [ ] Manager: Be sure to introduce the transitioning team member in the next team call. Ask them to share insights into their professional background, their interest in joining the team, where they are located, and what activities they enjoy outside of work.
1. [ ] Manager: Check whether [a probationary period is included in the location of the team member](https://about.gitlab.com/handbook/people-group/contracts-and-international-expansion/#probation-periods-of-team-members-employed-through-a-peo) and whether it has ended or is still running. If still running ensure to gather information needed to make the decision when that probationary period ends.
......
......@@ -44,7 +44,7 @@ In the interests of paying it forward and contributing to our core values of Col
1. [ ] Enable "self-service" in BambooHR by clicking the orange gear at the top right, hovering over "BambooHR Access Level" and selecting "Employee self-service."
1. [ ] Depending on the team members location, please ping the relevant payroll contact persons in this issue to notify them that the team member is active again i.e. US and Canada: Ann Tiseo and Cristine Marquardt and Non-US: Harley Devlin and Nicole Precilla
1. [ ] Update the Status in BambooHR under the Personal Tab to Active. This should be done the business day prior to the team member coming back.
1. [ ] :red_circle: Ping the ITOps team (`@gitlab-com/business-ops/team-member-enablement`) in this issue to reactivate all the accounts for the new team member.
1. [ ] :red_circle: Ping the ITOps team (`@gitlab-com/business-technology/team-member-enablement`) in this issue to reactivate all the accounts for the new team member.
1. [ ] Schedule a GSuite Email Reset to arrive at 7 am local time
1. [ ] Schedule a Welcome back email and include this Career Mobility Issue Link
......@@ -75,7 +75,7 @@ In the interests of paying it forward and contributing to our core values of Col
1. [ ] Review the team member's current access and submit an [Access Change Request](https://gitlab.com/gitlab-com/team-member-epics/access-requests/issues/new?issuable_template=Access_Change_Request) issue. Please work with the New Reporting Manager to determine if a team member's access will still be needed in the new role or if access will need to be updated to a higher/lower access role. Please cc the new manager.
1. [ ] Coordinate with IT Ops to change any shared passwords, with the intent to be gated behind Okta when possible, in particular;
1. [ ] Review if team member has sysadmin access passwords for GitLab.com Infrastructure (ssh, chef user/key, others). Identify if any can be moved to Okta.
1. [ ] Review what 1Password vaults team member had access to, and identify any shared passwords to be changed and moved to Okta. If team member has access to any shared passwords that will no longer be relevant to their new role, please ping `@gitlab-com/business-ops/team-member-enablement` and coordinate shared account password rotation.
1. [ ] Review what 1Password vaults team member had access to, and identify any shared passwords to be changed and moved to Okta. If team member has access to any shared passwords that will no longer be relevant to their new role, please ping `@gitlab-com/business-technology/team-member-enablement` and coordinate shared account password rotation.
1. [ ] Remove any scheduled 1:1 meetings with the team member.
</details>
......@@ -93,7 +93,7 @@ In the interests of paying it forward and contributing to our core values of Col
1. [ ] Invite team member to recurring team meetings.
1. [ ] Schedule weekly [1:1 meetings](https://about.gitlab.com/handbook/leadership/1-1/) with new team member. Use the first 15 minutes to get to know your new team member on a personal level.
1. [ ] Set new GitLab team members' project-level permissions as-needed.
1. [ ] Add the new team member to the required groups in 1Password if you have access to the Admin Console in 1Password. If you do not have access please ping @gitlab-com/business-ops/team-member-enablement with which vaults the new team member should be added to. Note: if it is necessary to add an individual to a vault (instead of to a group), make sure that the permissions are set to _not allow_ exporting items.
1. [ ] Add the new team member to the required groups in 1Password if you have access to the Admin Console in 1Password. If you do not have access please ping @gitlab-com/business-technology/team-member-enablement with which vaults the new team member should be added to. Note: if it is necessary to add an individual to a vault (instead of to a group), make sure that the permissions are set to _not allow_ exporting items.
1. [ ] Introduce your new team member to your team at your next team call. Ask them to tell the team about where they were before GitLab, why they wanted to join the team, where they are located, and what they like to do for fun outside of work.
1. [ ] Review [GitLab's Probation Period Process](https://about.gitlab.com/handbook/people-group/contracts-and-international-expansion/#probation-period) and check if your new team member falls within a country that has a probation period. This is important as the People Experience team will be following up with you to review the probation period, within the period on the linked page.
......@@ -133,7 +133,7 @@ In the interests of paying it forward and contributing to our core values of Col
1. [ ] Read 1Password's [getting started guides](https://support.1password.com/explore/extension/) and the [Mac app](https://support.1password.com/getting-started-mac/) to understand its functionality.
1. [ ] Ensure that your 1Password master key is unique and random. Start learning it!
#### Okta
1. [ ] :red_circle: Check that your Okta Account is active. Reminder: GitLab uses Okta as its primary portal for all SaaS Applications. Okta will populate your Dashboard with many of the Applications you will need, but some of these will require activation. Read and Review the [Okta Handbook](https://about.gitlab.com/handbook/business-ops/okta/) page for more information. If inactive, please ping ITOPs (`@gitlab-com/business-ops/team-member-enablement`) in this issue for further assistance.
1. [ ] :red_circle: Check that your Okta Account is active. Reminder: GitLab uses Okta as its primary portal for all SaaS Applications. Okta will populate your Dashboard with many of the Applications you will need, but some of these will require activation. Read and Review the [Okta Handbook](https://about.gitlab.com/handbook/business-technology/okta/) page for more information. If inactive, please ping ITOPs (`@gitlab-com/business-technology/team-member-enablement`) in this issue for further assistance.
1. [ ] Reset your GitLab password via Okta if needed. Make sure that you start from the [Okta dashboard](https://gitlab.okta.com/app/UserHome) to log into your GitLab account. Do this by clicking the GitLab.com tile directly from your Okta dashboard.
1. [ ] Reset your Google password via Okta if needed and re set up 2FA for your Google account.
1. [ ] Reset any additional existing passwords in line with the security training & guidelines, if needed.
......
......@@ -32,10 +32,10 @@ Completion of the tasks detailed in the offboarding issue ensures that GitLab re
<details>
<summary>Manager</summary>
1. [ ] Please comment, tagging the IT Ops team `@gitlab-com/business-ops/team-member-enablement` if you need delegate access to the former Gitlab Team Member's email account.
1. [ ] Please comment, tagging the IT Ops team `@gitlab-com/business-ops/team-member-enablement` if you need the former Gitlab Team member's Google Drive transferred at the time of offboarding.
1. [ ] Please comment, tagging the IT Ops team `@gitlab-com/business-technology/team-member-enablement` if you need delegate access to the former Gitlab Team Member's email account.
1. [ ] Please comment, tagging the IT Ops team `@gitlab-com/business-technology/team-member-enablement` if you need the former Gitlab Team member's Google Drive transferred at the time of offboarding.
1. [ ] Manager: Review all open merge requests and issues assigned to the team member and reassign them to you or another team member as per your handover agreement within the team.
1. [ ] Coordinate with IT Ops @gitlab-com/business-ops/team-member-enablement to change any shared passwords, with the intent to be gated behind Okta when possible, in particular;
1. [ ] Coordinate with IT Ops @gitlab-com/business-technology/team-member-enablement to change any shared passwords, with the intent to be gated behind Okta when possible, in particular;
1. [ ] Review if team member had sysadmin access passwords for GitLab.com Infrastructure (ssh, chef user/key, others). Identify if any can be moved to Okta.
1. [ ] Review what 1Password vaults former team member had access to, and identify any shared passwords to be changed and moved to Okta.
1. [ ] In the #team-member-updates on Slack, announce departure of team member as soon as the chat and Google Accounts are blocked with the ['X is no longer with GitLab template'](https://about.gitlab.com/handbook/people-group/offboarding/#communicating-departures-company-wide). Do not say anything about reason for offboarding for involuntary offboarding.
......@@ -153,20 +153,20 @@ _Note: This will also trigger any deprovisioning workflows for Applications that
1. [ ] IT Ops: Select the dropdown icon `ˇ` in the `User information` section and delete the email alias associated with the user.
1. [ ] IT Ops: Following the [instructions in the Handbook](https://about.gitlab.com/handbook/people-group/offboarding/offboarding_guidelines/#g-suite), set an automatic rejection rule. This sends an auto-response to the sender notifying them that the team member is no longer with GitLab and who to contact instead.
1. [ ] IT Ops: As per the Manager's comment in this issue (ping them if they haven't commented yet), please transfer ownership of documents to the Manager, if so requested.
1. [ ] IT Ops @gitlab-com/business-ops/team-member-enablement : Check if former GitLab Team Member had a gold account on GitLab and if so, downgrade the account.
1. [ ] IT Ops @gitlab-com/business-technology/team-member-enablement : Check if former GitLab Team Member had a gold account on GitLab and if so, downgrade the account.
- If needed, you can find who has a gold account by searching in the [ARs project](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/issues?scope=all&utf8=%E2%9C%93&state=closed&label_name[]=GitLab%20Gold%20Request) and the [Gold Entitlement Request project](https://gitlab.com/gitlab-com/team-member-epics/gold-entitlement-request/-/issues?scope=all&utf8=%E2%9C%93&state=all)) for Closed `~"GitLab Gold Request"`s. You can use the `author` filter to narrow it down if needed.
1. [ ] IT Ops @gitlab-com/business-ops/team-member-enablement : Remove former GitLab Team Member's' GitLab.com account from the [gitlab-com group](https://gitlab.com/groups/gitlab-com/-/group_members).
1. [ ] IT Ops @gitlab-com/business-ops/team-member-enablement : Block former GitLab Team Member, remove from all company Groups and Projects, and remove GitLab job role if visible on profile.
1. [ ] IT Ops @gitlab-com/business-ops/team-member-enablement : **IF** the former GitLab Team Member's start date was **prior to 2020-03-23**, change the primary email address on the GitLab.com account to be a personal email address of the former Team Member and unblock the account.
1. [ ] IT Ops @gitlab-com/business-ops/team-member-enablement : Remove former GitLabber's admin account, if applicable.
1. [ ] IT Ops @gitlab-com/business-ops/team-member-enablement : Block former GitLab Team Member's [dev.GitLab.org account](https://dev.gitlab.org/admin/users) and remove from [gitlab group](https://dev.gitlab.org/groups/gitlab/group_members).
1. [ ] IT Ops @gitlab-com/business-ops/team-member-enablement : Block former GitLab Team Member's [staging.GitLab.com account](https://staging.gitlab.com/admin/users) and remove from [gitlab group](https://staging.gitlab.com/groups/gitlab/group_members).
1. [ ] IT Ops @gitlab-com/business-technology/team-member-enablement : Remove former GitLab Team Member's' GitLab.com account from the [gitlab-com group](https://gitlab.com/groups/gitlab-com/-/group_members).
1. [ ] IT Ops @gitlab-com/business-technology/team-member-enablement : Block former GitLab Team Member, remove from all company Groups and Projects, and remove GitLab job role if visible on profile.
1. [ ] IT Ops @gitlab-com/business-technology/team-member-enablement : **IF** the former GitLab Team Member's start date was **prior to 2020-03-23**, change the primary email address on the GitLab.com account to be a personal email address of the former Team Member and unblock the account.
1. [ ] IT Ops @gitlab-com/business-technology/team-member-enablement : Remove former GitLabber's admin account, if applicable.
1. [ ] IT Ops @gitlab-com/business-technology/team-member-enablement : Block former GitLab Team Member's [dev.GitLab.org account](https://dev.gitlab.org/admin/users) and remove from [gitlab group](https://dev.gitlab.org/groups/gitlab/group_members).
1. [ ] IT Ops @gitlab-com/business-technology/team-member-enablement : Block former GitLab Team Member's [staging.GitLab.com account](https://staging.gitlab.com/admin/users) and remove from [gitlab group](https://staging.gitlab.com/groups/gitlab/group_members).
1. [ ] IT Ops: [Check if the team member has created any Slack bots](https://about.gitlab.com/handbook/people-group/offboarding/offboarding_guidelines/) before disabling account. [Link](https://gitlab.slack.com/apps/manage?utm_source=in-prod&utm_medium=inprod-apps_link-slack_menu-click) to Apps menu.
1. [ ] IT Ops: Disable team member in [Slack](https://gitlab.slack.com/admin). If the team member is an Admin ping @pkaldis to remove them.
1. [ ] IT Ops: Okta should now deprovision 1Password as part of Okta Deactivation, please verify it was deactivated. If not, please ping the team in the #it-help Slack channel.
1. [ ] IT Ops: Reach out to former team member to identify and retrieve any company supplies/equipment. @gitlab-com/business-ops/team-member-enablement See the [Offboarding page](https://about.gitlab.com/handbook/people-group/offboarding/) for further details on that process.
1. [ ] IT Ops @gitlab-com/business-ops/team-member-enablement : Comment in this issue when equipment has been returned/recycled. Ping hiring manager, Security and `@Courtney_cote`.
1. [ ] IT Ops @gitlab-com/business-ops/team-member-enablement : Inform Controller / Accounting if any items in former GitLab Team Member's possession will not be returning, so that they can be removed from asset tracking.
1. [ ] IT Ops: Reach out to former team member to identify and retrieve any company supplies/equipment. @gitlab-com/business-technology/team-member-enablement See the [Offboarding page](https://about.gitlab.com/handbook/people-group/offboarding/) for further details on that process.
1. [ ] IT Ops @gitlab-com/business-technology/team-member-enablement : Comment in this issue when equipment has been returned/recycled. Ping hiring manager, Security and `@Courtney_cote`.
1. [ ] IT Ops @gitlab-com/business-technology/team-member-enablement : Inform Controller / Accounting if any items in former GitLab Team Member's possession will not be returning, so that they can be removed from asset tracking.
1. [ ] IT Ops: Okta should now deprovision Zoom as part of Okta Deactivation, please verify it was deactivated. If not, please ping the team in the #it-help Slack channel.
1. [ ] IT Ops: After 5 days, when the former team member's offboarding issue is due, delete their GSuite account now referred 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 manager task to see whether they have requested to have Document ownership transferred to them, or if they have agreed to not receive ownership. Delete the team members Google account 5 days after the offboarding date.
1. [ ] IT Ops: Remove access to Loom if person had access
......@@ -296,7 +296,7 @@ Review the table of applications listed below that is included in our [Tech Stac
</table>
#### <summary> @gitlab-com/business-ops/team-member-enablement </summary>
#### <summary> @gitlab-com/business-technology/team-member-enablement </summary>
<table >
<tbody>
......@@ -513,7 +513,7 @@ Review the table of applications listed below that is included in our [Tech Stac
## Finance
#### <summary> Finance Ops/Finance System Admins @gitlab-com/business-ops/enterprise-apps/financeops </summary>
#### <summary> Finance Ops/Finance System Admins @gitlab-com/business-technology/enterprise-apps/financeops </summary>
<table >
<tbody>
......
......@@ -29,7 +29,7 @@ To ensure a successful completion of the issue, it is important that all tasks a
<summary>Manager</summary>
1. [ ] Manager: Review all open merge requests and issues assigned to the team member and reassign them to you or another team member as per your handover agreement within the team.
1. [ ] Coordinate with IT Ops @gitlab-com/business-ops/team-member-enablement to change any shared passwords, with the intent to be gated behind Okta when possible, in particular;
1. [ ] Coordinate with IT Ops @gitlab-com/business-technology/team-member-enablement to change any shared passwords, with the intent to be gated behind Okta when possible, in particular;
1. [ ] Review if team member had sysadmin access passwords for GitLab.com Infrastructure (ssh, chef user/key, others). Identify if any can be moved to Okta.
1. [ ] Organize a smooth hand over of any work or tasks from the interns.
1. [ ] Scroll to the bottom of this issue; depending on the department, division, or entity there may be additional manager tasks.
......@@ -75,11 +75,11 @@ _Note: This will also trigger any deprovisioning workflows for Applications that
1. [ ] IT Ops: Click the `More` button (left hand side of screen) and then click `Suspend User` and click it again to confirm. This will ensure that the user can no longer access their account.
1. [ ] IT Ops: Deactivate the user from all groups they are associated with.
1. [ ] IT Ops: Following the [instructions in the Handbook](https://about.gitlab.com/handbook/people-group/offboarding/offboarding_guidelines/#g-suite), set an automatic rejection rule. This sends an auto-response to the sender notifying them that the team member is no longer with GitLab and who to contact instead.
1. [ ] IT Ops @gitlab-com/business-ops/team-member-enablement : Deactivate Interns GitLab.com account from the [gitlab-com group](https://gitlab.com/groups/gitlab-com/-/group_members).
1. [ ] IT Ops @gitlab-com/business-ops/team-member-enablement : Temporarily block the Intern, remove from all company Groups and Projects, and remove GitLab job role if visible on profile.
1. [ ] IT Ops @gitlab-com/business-ops/team-member-enablement : Deactivate the Interns admin account, if applicable.
1. [ ] IT Ops @gitlab-com/business-ops/team-member-enablement : Deactivate former GitLab Team Member's [dev.GitLab.org account](https://dev.gitlab.org/admin/users) and remove from [gitlab group](https://dev.gitlab.org/groups/gitlab/group_members).
1. [ ] IT Ops @gitlab-com/business-ops/team-member-enablement : Deactivate former GitLab Team Member's [staging.GitLab.com account](https://staging.gitlab.com/admin/users) and [gitlab group](https://staging.gitlab.com/groups/gitlab/group_members).
1. [ ] IT Ops @gitlab-com/business-technology/team-member-enablement : Deactivate Interns GitLab.com account from the [gitlab-com group](https://gitlab.com/groups/gitlab-com/-/group_members).
1. [ ] IT Ops @gitlab-com/business-technology/team-member-enablement : Temporarily block the Intern, remove from all company Groups and Projects, and remove GitLab job role if visible on profile.
1. [ ] IT Ops @gitlab-com/business-technology/team-member-enablement : Deactivate the Interns admin account, if applicable.
1. [ ] IT Ops @gitlab-com/business-technology/team-member-enablement : Deactivate former GitLab Team Member's [dev.GitLab.org account](https://dev.gitlab.org/admin/users) and remove from [gitlab group](https://dev.gitlab.org/groups/gitlab/group_members).
1. [ ] IT Ops @gitlab-com/business-technology/team-member-enablement : Deactivate former GitLab Team Member's [staging.GitLab.com account](https://staging.gitlab.com/admin/users) and [gitlab group](https://staging.gitlab.com/groups/gitlab/group_members).
1. [ ] IT Ops: [Check if the team member has created any Slack bots](https://about.gitlab.com/handbook/people-group/offboarding/offboarding_guidelines/) before disabling account. [Link](https://gitlab.slack.com/apps/manage?utm_source=in-prod&utm_medium=inprod-apps_link-slack_menu-click) to Apps menu.
1. [ ] IT Ops: Temporarily disable the Intern in [Slack](https://gitlab.slack.com/admin).
1. [ ] IT Ops: Log into [1Password](https://1password.com/) and click on "People" in the right-hand sidebar. Search for the team member's name. Click "More Actions" under their name and choose "Suspend" to remove access to 1Password. Take a screenshot of the user's permissions and post it as a comment in this offboarding issue.
......@@ -144,7 +144,7 @@ Review the table of applications listed below that is included in our [Tech Stac
1. [ ] WebEx
<summary> @gitlab-com/business-ops/team-member-enablement </summary>
<summary> @gitlab-com/business-technology/team-member-enablement </summary>
1. [ ] LucidChart
......
......@@ -18,8 +18,8 @@
<summary>IT Ops</summary>
1. [ ] IT Ops @gitlab-com/business-ops/team-member-enablement : Remove any development VMs and other resources:
1. [ ] IT Ops @gitlab-com/business-technology/team-member-enablement : Remove any development VMs and other resources:
- [ ] Notifiy one of the deprovisioners listed for [AWS](https://console.aws.amazon.com/) in our [Tech Stack](https://docs.google.com/spreadsheets/d/1mTNZHsK3TWzQdeFqkITKA0pHADjuurv37XMuHv12hDU/edit#gid=1906611965)
- [ ] Send a merge request to [the dev-resources repo](https://gitlab.com/gitlab-com/dev-resources) to remove `dev-resources/name-surname.tf`. Follow the instructions [here](https://gitlab.com/gitlab-com/dev-resources/tree/master/dev-resources#how-do-i-delete-an-instance-i-dont-need-anymore).
- [ ] Delete all of the team member's branches from [support-resources](https://gitlab.com/gitlab-com/support/support-resources/-/branches) to delete their GCP instances
1. [ ] IT Ops @gitlab-com/business-ops/team-member-enablement : Revoke GitLab.com admin access if they had it. If you're not sure (i.e. their access predates access requests) ping the manager.
1. [ ] IT Ops @gitlab-com/business-technology/team-member-enablement : Revoke GitLab.com admin access if they had it. If you're not sure (i.e. their access predates access requests) ping the manager.
......@@ -11,7 +11,7 @@
<summary>IT Ops</summary>
1. [ ] IT Ops @gitlab-com/business-ops/team-member-enablement : remove team member from the `@uxers` User Group on Slack.
1. [ ] IT Ops @gitlab-com/business-technology/team-member-enablement : remove team member from the `@uxers` User Group on Slack.
<summary>Other</summary>
......
......@@ -11,7 +11,7 @@
<summary>IT Ops</summary>
1. [ ] IT Ops @gitlab-com/business-ops/team-member-enablement : Remove any development VMs. Send a merge request to [the dev-resources repo](https://gitlab.com/gitlab-com/dev-resources) to remove `dev-resources/name-surname.tf`. Follow the instructions [here](https://gitlab.com/gitlab-com/dev-resources/tree/master/dev-resources#how-do-i-delete-an-instance-i-dont-need-anymore).
1. [ ] IT Ops @gitlab-com/business-technology/team-member-enablement : Remove any development VMs. Send a merge request to [the dev-resources repo](https://gitlab.com/gitlab-com/dev-resources) to remove `dev-resources/name-surname.tf`. Follow the instructions [here](https://gitlab.com/gitlab-com/dev-resources/tree/master/dev-resources#how-do-i-delete-an-instance-i-dont-need-anymore).
<summary>Product Licenses</summary>
......
......@@ -70,7 +70,7 @@ This is another opportunity for the People Experience Team to evolve and improve
1. [ ] Send an email to the chosen buddy `MANAGER__PLACE__BUDDY_HANDLE__HERE` letting them know that they have been chosen, and include a link to the onboarding issue.
1. [ ] Assign the onboarding buddy to this issue by clicking Edit in the Assignees section (right-hand column) and enter the buddy GitLab handle. Please also update the onboarding `__BUDDY_HANDLE__` in the top intro section of this issue with the buddy handle by clicking edit in this issue. This will allow the onboarding buddy to have even further transparency and awareness on how the new team member is doing.
1. [ ] We encourage managers to review their schedule and ensure availability to support onboarding team members ahead of their pre-determined start date. In an instance where you may be OOO please be sure to nominate another individual from within the department for this purpose.
1. [ ] The default laptop for the new team member will be an Apple MacBook Pro. If the new team member could benefit from using a Dell with Linux instead, remind the new team member to request it. Details and the appropriate information on laptops are included in the "Welcome" email sent to the new team member from the CES team after the team member's offer is signed, but many are overwhelmed with paperwork and new job excitement, so a friendly reminder might be in order. Refer to the handbook for more information on [approved laptops](https://about.gitlab.com/handbook/business-ops/team-member-enablement/onboarding-access-requests/#laptop-configurations).
1. [ ] The default laptop for the new team member will be an Apple MacBook Pro. If the new team member could benefit from using a Dell with Linux instead, remind the new team member to request it. Details and the appropriate information on laptops are included in the "Welcome" email sent to the new team member from the CES team after the team member's offer is signed, but many are overwhelmed with paperwork and new job excitement, so a friendly reminder might be in order. Refer to the handbook for more information on [approved laptops](https://about.gitlab.com/handbook/business-technology/team-member-enablement/onboarding-access-requests/#laptop-configurations).
1. [ ] Schedule a Zoom video call with the new team member for the start of their first day to welcome them to the team and set expectations. Send them an invitation to their personal email. The team members GitLab email address will only be activated on their first day.
1. [ ] Send an email to the new team member's personal email address welcoming them to GitLab. Provide them with the time and Zoom link to the introduction video call as well as any other information the manager feels will help with a great first day experience.
1. [ ] Read through the [Building Trust Handbook page](https://about.gitlab.com/handbook/people-group/learning-and-development/building-trust/). All people leaders have a responsibility to get to know their people to understand how someone would like to receive feedback.
......@@ -215,10 +215,10 @@ These steps need to happen 1 day prior to the new hire's start date. This will e
#### Day 2
1. [ ] A [role based entitlement Access Request](https://about.gitlab.com/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/baseline-entitlements/#role-entitlements-for-a-specific-job) will be created automatically for new team members **if** a [pre-approved template exists](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/tree/master/.gitlab/issue_templates/role_baseline_access_request_tasks) and you will be tagged in it automatically (starting 2020-Apr). The AR will also be automatically added to the new team member epic together with their onboarding issue. The AR should request access to anything NOT provided by [baseline entitlements for all GitLab team members](https://about.gitlab.com/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/baseline-entitlements/#baseline-entitlements-all-gitlab-team-members).
1. [ ] A [role based entitlement Access Request](https://about.gitlab.com/handbook/business-technology/team-member-enablement/onboarding-access-requests/access-requests/baseline-entitlements/#role-entitlements-for-a-specific-job) will be created automatically for new team members **if** a [pre-approved template exists](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/tree/master/.gitlab/issue_templates/role_baseline_access_request_tasks) and you will be tagged in it automatically (starting 2020-Apr). The AR will also be automatically added to the new team member epic together with their onboarding issue. The AR should request access to anything NOT provided by [baseline entitlements for all GitLab team members](https://about.gitlab.com/handbook/business-technology/team-member-enablement/onboarding-access-requests/access-requests/baseline-entitlements/#baseline-entitlements-all-gitlab-team-members).
- As the manager, please check if the AR covers the correct entitlements.
- If the AR was not created AND a role baseline entitlement exists for the role, please create an [issue for People Ops Engineering](https://gitlab.com/gitlab-com/people-group/people-operations-engineering/-/issues/new) and proceed with manually creating the AR for the new team member. If creating it manually, don't forget to include the [person's details](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/blob/master/.gitlab/issue_templates/role_baseline_access_request.md) in the issue.
- For all other roles that do not have a role-specific AR template, open a [Individual or Bulk Access Request](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/issues/new?issuable_template=Individual_Bulk_Access_Request). We recommend [creating a role based entitlements template](https://about.gitlab.com/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/baseline-entitlements/#how-do-i-create-a-role-based-entitlement-template) so all future team members with a role get the AR created automatically.
- For all other roles that do not have a role-specific AR template, open a [Individual or Bulk Access Request](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/issues/new?issuable_template=Individual_Bulk_Access_Request). We recommend [creating a role based entitlements template](https://about.gitlab.com/handbook/business-technology/team-member-enablement/onboarding-access-requests/access-requests/baseline-entitlements/#how-do-i-create-a-role-based-entitlement-template) so all future team members with a role get the AR created automatically.
</details>
......@@ -263,8 +263,8 @@ These steps need to happen 1 day prior to the new hire's start date. This will e
1. [ ] :red_circle: Complete the [survey/feedback](https://docs.google.com/forms/d/1_jUbA961Mj44paTfiI2VFTMsElAdjEqFsLrfPKfoW04) form for the Security Orientation training.
1. [ ] :red_circle: Read our [Security Practices](https://about.gitlab.com/handbook/security) page, especially our Password Policy Guidelines.
1. [ ] :red_circle: Jamf enrollment - *Mac only*
- If you have self-procured your machine, please make sure to enroll in [Jamf](https://about.gitlab.com/handbook/business-ops/team-member-enablement/onboarding-access-requests/endpoint-management/#enrolling-in-jamf).
- If the company has procured the machine for you, please confirm that [Jamf is installed correctly](https://about.gitlab.com/handbook/business-ops/team-member-enablement/onboarding-access-requests/endpoint-management/#installation-completion-confirmation). If not, please follow the steps to [enroll in [Jamf](https://about.gitlab.com/handbook/business-ops/team-member-enablement/onboarding-access-requests/endpoint-management/#enrolling-in-jamf). Please ask any questions in the `#it_help` Slack channel.
- If you have self-procured your machine, please make sure to enroll in [Jamf](https://about.gitlab.com/handbook/business-technology/team-member-enablement/onboarding-access-requests/endpoint-management/#enrolling-in-jamf).
- If the company has procured the machine for you, please confirm that [Jamf is installed correctly](https://about.gitlab.com/handbook/business-technology/team-member-enablement/onboarding-access-requests/endpoint-management/#installation-completion-confirmation). If not, please follow the steps to [enroll in [Jamf](https://about.gitlab.com/handbook/business-technology/team-member-enablement/onboarding-access-requests/endpoint-management/#enrolling-in-jamf). Please ask any questions in the `#it_help` Slack channel.
##### 1Password
......@@ -276,7 +276,7 @@ These steps need to happen 1 day prior to the new hire's start date. This will e
1. [ ] Before saving passwords in 1Password, understand why some will be in 1Password versus Okta. For passwords that cannot be saved in Okta, remember to save your passwords in your [*Private* vault](https://support.1password.com/1password-com-items/) (only accessible to you) rather than a shared vault (accessible to others at GitLab).
1. [ ] Create a secure password for your laptop lock screen.
##### Okta
1. [ ] :red_circle: Set up your Okta Account. GitLab uses Okta as its primary portal for all SaaS Applications, and you should already have an activation email in both your Gmail and Personal Accounts. Okta will populate your Dashboard with many of the Applications you will need, but some of these will require activation. Read and Review the [Okta Handbook](https://about.gitlab.com/handbook/business-ops/okta/) page for more information.
1. [ ] :red_circle: Set up your Okta Account. GitLab uses Okta as its primary portal for all SaaS Applications, and you should already have an activation email in both your Gmail and Personal Accounts. Okta will populate your Dashboard with many of the Applications you will need, but some of these will require activation. Read and Review the [Okta Handbook](https://about.gitlab.com/handbook/business-technology/okta/) page for more information.
1. [ ] Reset your GitLab password via Okta. Make sure that you start from the [Okta dashboard](https://gitlab.okta.com/app/UserHome) to log into your GitLab account. Do this by clicking the GitLab.com tile directly from your Okta dashboard.
1. [ ] Reset your Google password via Okta and set up 2FA for your Google account immediately.
1. [ ] If you created any accounts while onboarding before being added to Okta, add these passwords to the relevant Okta Application.
......@@ -433,9 +433,9 @@ On your calendar, you will have a invites to the below meetings, they are option
1. [ ] Your GitLab.com account must use your GitLab email and must only be used for GitLab related purposes, so make sure notifications are being sent to your `@gitlab.com` email.
1. [ ] Consider enabling notifications about your own activity (helpful for visibility in later Git steps). To enable this, go to Settings -> Notifications -> Check the box before "Receive notifications about your own activity"
1. [ ] If you are already in possession of a company owned Apple laptop for use in your new role at Gitlab, please create or update the Apple ID, using your GitLab email address. If you have [problems creating an apple ID from system preferences](https://discussions.apple.com/thread/8438000), try creating it through the [App Store](https://support.apple.com/en-us/HT204316). If an app is critical to your work, it can be reimbursed through Expensify. If your laptop is of a different make, please assign any computer or store ID to your GitLab email address.
1. [ ] :red_circle: Encrypt your Hard Drive - instructions for both Apple and Linux machines can be found [here](https://about.gitlab.com/handbook/business-ops/team-member-enablement/onboarding-access-requests/#full-disk-encryption) with additional information around the Linux set-up process [here](https://about.gitlab.com/handbook/tools-and-tips/linux/#initial-installation).
1. [ ] :red_circle: Encrypt your Hard Drive - instructions for both Apple and Linux machines can be found [here](https://about.gitlab.com/handbook/business-technology/team-member-enablement/onboarding-access-requests/#full-disk-encryption) with additional information around the Linux set-up process [here](https://about.gitlab.com/handbook/tools-and-tips/linux/#initial-installation).
1. [ ] :red_circle: Leave a comment in this issue with a screenshot to verify that your hard drive is encrypted with the serial number of your computer for correlation.
1. [ ] Please review the [Full Disk Encryption](https://about.gitlab.com/handbook/business-ops/team-member-enablement/onboarding-access-requests/#full-disk-encryption) page in the handbook for the appropriate steps to create the screenshot with the necessary information.
1. [ ] Please review the [Full Disk Encryption](https://about.gitlab.com/handbook/business-technology/team-member-enablement/onboarding-access-requests/#full-disk-encryption) page in the handbook for the appropriate steps to create the screenshot with the necessary information.
1. [ ] To take a screenshot on an Apple machine press `Command` + `Shift` + `3` to take a screenshot of the entire desktop, alternativey `Command` + `Shift` + `4` will take a screenshot of the area you select. If you are using a Linux machine `Prt Scrn` will take a screenshot of the entire desktop; `Alt + Prt Scrn` will take a screenshot of a specific window and `Shift + Prt Scrn` will take a screenshot of an area you select.
1. [ ] To Upload the screenshot to your issue: Find the `Attach a file` link at the bottom of this issue and press Comment. Depending on the operating system you are using, the steps to retrieve this information may be different.
1. [ ] Please note that GitLab's [Internal Acceptable Use Policy](https://about.gitlab.com/handbook/people-group/acceptable-use-policy/#unacceptable-system-and-network-activities) prohibits the use of tools that capture and share screenshots to hosted third-party sites so please make sure that you do not leverage such a tool to complete this step.
......
......@@ -18,7 +18,7 @@ In addition to general onboarding, you may have Department- or role-specific tas
1. [ ] Select the mentor for the internship: this mentor will be providing extensive guidance throughout the internship. Please select someone in a similar time zone and someone that will not be on PTO the first 2 weeks. Ideally someone who has been at GitLab for at least 3 months would be helpful. It is highly encouraged that a mentor is selected for the new team member to have the best support during their onboarding. Review [Onboarding Buddies Handbook page](https://about.gitlab.com/handbook/people-group/general-onboarding/onboarding-buddies/) for more information.
1. [ ] Send an email to the chosen mentor `MANAGER__PLACE__BUDDY_HANDLE__HERE` letting them know that they have been chosen, and include a link to the onboarding issue.
1. [ ] Manager: The default laptop for the new team member will be an Apple MacBook Pro. If the new team member could benefit from using a Dell with Linux instead, remind the new team member to request it. Details and the appropriate information on laptops are included in the "Welcome" email sent to the new team member from the CES team after the team member's offer is signed, but many are overwhelmed with paperwork and new job excitement, so a friendly reminder might be in order. Refer to the handbook for more information on [approved laptops](https://about.gitlab.com/handbook/business-ops/team-member-enablement/onboarding-access-requests/#laptop-configurations).
1. [ ] Manager: The default laptop for the new team member will be an Apple MacBook Pro. If the new team member could benefit from using a Dell with Linux instead, remind the new team member to request it. Details and the appropriate information on laptops are included in the "Welcome" email sent to the new team member from the CES team after the team member's offer is signed, but many are overwhelmed with paperwork and new job excitement, so a friendly reminder might be in order. Refer to the handbook for more information on [approved laptops](https://about.gitlab.com/handbook/business-technology/team-member-enablement/onboarding-access-requests/#laptop-configurations).
. [ ] Manager: Schedule a Zoom video call with the new team member for the start of their first day to welcome them to the team and set expectations. Send them an invitation to both their personal email and GitLab email, as it is possible that they will not have created their Zoom account linked to their GitLab email by the time of this scheduled meeting.
1. [ ] Manager: Send an email to the new team member's personal email address welcoming them to GitLab. Provide them with the time and Zoom link to the introduction video call as well as any other information the manager feels will help with a great first day experience.
1. [ ] Manager: Update [vacancy entry or add entry to team page](https://about.gitlab.com/handbook/general-onboarding/onboarding-processes/#add-blank-entry-to-team-page-) (temporary slug, type, first name + initial, start date, title, and use `../gitlab-logo-extra-whitespace.png` for the picture). For story, add "Joining Month Xth".
......@@ -44,7 +44,7 @@ In addition to general onboarding, you may have Department- or role-specific tas
<details>
<summary>IT Ops</summary>
1. [ ] IT Ops @gitlab-com/business-ops/team-member-enablement : Order the new team member's laptop. If you are not able to ship a laptop to a specific country, let the new team member know and initiate discussion of purchase and expensing. (*NOTE* laptop orders can take up to 2-3+ weeks, especially in remote areas)
1. [ ] IT Ops @gitlab-com/business-technology/team-member-enablement : Order the new team member's laptop. If you are not able to ship a laptop to a specific country, let the new team member know and initiate discussion of purchase and expensing. (*NOTE* laptop orders can take up to 2-3+ weeks, especially in remote areas)
</details>
......@@ -161,7 +161,7 @@ In addition to general onboarding, you may have Department- or role-specific tas
1. [ ] New team member: Create a secure password for your laptop lock screen.
##### Okta
1. [ ] New team member: Set up your Okta Account. GitLab uses Okta as its primary portal for all SaaS Applications, and you should already have an activation email in both your Gmail and Personal Accounts. Okta will populate your Dashboard with many of the Applications you will need, but some of these will require activation. Read and Review the [Okta Handbook](https://about.gitlab.com/handbook/business-ops/okta/) page for more information.
1. [ ] New team member: Set up your Okta Account. GitLab uses Okta as its primary portal for all SaaS Applications, and you should already have an activation email in both your Gmail and Personal Accounts. Okta will populate your Dashboard with many of the Applications you will need, but some of these will require activation. Read and Review the [Okta Handbook](https://about.gitlab.com/handbook/business-technology/okta/) page for more information.
1. [ ] New team member: Reset your GitLab password via Okta. Make sure that you start from the [Okta dashboard](https://gitlab.okta.com/app/UserHome) to log into your GitLab account. Do this by clicking the GitLab.com tile directly from your Okta dashboard.
1. [ ] New team member: Reset your Google password via Okta and set up 2FA for your Google account immediately.
1. [ ] New team member: If you created any accounts while onboarding before being added to Okta, add these passwords to the relevant Okta Application.
......@@ -253,10 +253,10 @@ In addition to general onboarding, you may have Department- or role-specific tas
<summary>Manager</summary>
1. [ ] Manager: A [role based entitlement Access Request](https://about.gitlab.com/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/baseline-entitlements/#role-entitlements-for-a-specific-job) will be created automatically for new team members **if** a [pre-approved template exists](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/tree/master/.gitlab/issue_templates/role_baseline_access_request_tasks) and you will be tagged in it automatically (starting 2020-Apr). The AR will also be automatically added to the new team member epic together with their onboarding issue. The AR should request access to anything NOT provided by [baseline entitlements for all GitLab team members](https://about.gitlab.com/handbook/engineering/security/#baseline-entitlements-all-gitlab-team-members).
1. [ ] Manager: A [role based entitlement Access Request](https://about.gitlab.com/handbook/business-technology/team-member-enablement/onboarding-access-requests/access-requests/baseline-entitlements/#role-entitlements-for-a-specific-job) will be created automatically for new team members **if** a [pre-approved template exists](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/tree/master/.gitlab/issue_templates/role_baseline_access_request_tasks) and you will be tagged in it automatically (starting 2020-Apr). The AR will also be automatically added to the new team member epic together with their onboarding issue. The AR should request access to anything NOT provided by [baseline entitlements for all GitLab team members](https://about.gitlab.com/handbook/engineering/security/#baseline-entitlements-all-gitlab-team-members).
- As the manager, please check if the AR covers the correct entitlements.
- If the AR was not created AND a role baseline entitlement exists for the role, please create an [issue for People Ops Engineering](https://gitlab.com/gitlab-com/people-group/people-operations-engineering/-/issues/new) and proceed with manually creating the AR for the new team member. If creating it manually, don't forget to include the [person's details](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/blob/master/.gitlab/issue_templates/role_baseline_access_request.md) in the issue.
- For all other roles that do not have a role-specific AR template, open a [Single Person Access Request](https://gitlab.com/gitlab-com/team-member-epics/access-requests/issues/new?issuable_template=Single_Person_Access_Request). We recommend [creating a role based entitlements template](https://about.gitlab.com/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/baseline-entitlements/#how-do-i-create-a-role-based-entitlement-template) so all future team members with a role get the AR created automatically.
- For all other roles that do not have a role-specific AR template, open a [Single Person Access Request](https://gitlab.com/gitlab-com/team-member-epics/access-requests/issues/new?issuable_template=Single_Person_Access_Request). We recommend [creating a role based entitlements template](https://about.gitlab.com/handbook/business-technology/team-member-enablement/onboarding-access-requests/access-requests/baseline-entitlements/#how-do-i-create-a-role-based-entitlement-template) so all future team members with a role get the AR created automatically.
</details>
......@@ -317,7 +317,7 @@ In addition to general onboarding, you may have Department- or role-specific tas
1. [ ] New team member: Consider enabling notifications about your own activity (helpful for visibility in later Git steps). To enable this, go to Settings -> Notifications -> Check the box before "Receive notifications about your own activity"
1. [ ] New team member: If you are already in possession of a company owned Apple laptop for use in your new role at Gitlab, please create or update the Apple ID, using your GitLab email address. If an app is critical to your work, it can be reimbursed through Expensify. If your laptop is of a different make, please assign any computer or store ID to your GitLab email address.
1. [ ] New team member: Encrypt your hard drive. On Macs this may be with FileVault (see [security practices](https://about.gitlab.com/handbook/security) for help and more details).
1. [ ] New team member: Leave a comment in this issue with a screenshot verifying that your hard drive is encrypted (on Mac, `Command` + `Shift` + `3` for the entire screen or `Command` + `Shift` + `4` to decide which area you'd like to screenshot). To do this, find the `Attach a file` link at the bottom of this issue and press Comment. Please be sure that the screenshot includes your machine's serial number as well as evidence of disk encryption for correlation. Depending on the operating system you are using, the steps to retrieve this information may be different. Please review the [Full Disk Encryption](https://about.gitlab.com/handbook/business-ops/team-member-enablement/onboarding-access-requests/#full-disk-encryption) page in the handbook for the appropriate steps to create the screenshot with the necessary information. Please note that GitLab's [Internal Acceptable Use Policy](https://about.gitlab.com/handbook/people-group/acceptable-use-policy/#unacceptable-system-and-network-activities) prohibits the use of tools that capture and share screenshots to hosted third-party sites so please make sure that you do not leverage such a tool to complete this step.
1. [ ] New team member: Leave a comment in this issue with a screenshot verifying that your hard drive is encrypted (on Mac, `Command` + `Shift` + `3` for the entire screen or `Command` + `Shift` + `4` to decide which area you'd like to screenshot). To do this, find the `Attach a file` link at the bottom of this issue and press Comment. Please be sure that the screenshot includes your machine's serial number as well as evidence of disk encryption for correlation. Depending on the operating system you are using, the steps to retrieve this information may be different. Please review the [Full Disk Encryption](https://about.gitlab.com/handbook/business-technology/team-member-enablement/onboarding-access-requests/#full-disk-encryption) page in the handbook for the appropriate steps to create the screenshot with the necessary information. Please note that GitLab's [Internal Acceptable Use Policy](https://about.gitlab.com/handbook/people-group/acceptable-use-policy/#unacceptable-system-and-network-activities) prohibits the use of tools that capture and share screenshots to hosted third-party sites so please make sure that you do not leverage such a tool to complete this step.
1. [ ] New team member: Please add your serial code for your GitLab laptop here: [GitLab Notebook information](https://docs.google.com/forms/d/e/1FAIpQLSeUOlP11qeLdLZHTI62CFr7MSHAoI_1M6CRpnUA6fegkEKCOQ/viewform?usp=sf_link). You will need the evidence of full disk encryption from the previous step.
1. [ ] New team member: For contractors, it may be useful to save an invoice template for future use. An invoice template can be found in Google Docs by searching `Invoice Template` or [here](https://docs.google.com/spreadsheets/d/1CxJMQ06GK_DCqihVaZ0PXxNhumQYzgG--nw_ibPV0XA/edit#gid=0).
1. [ ] New team member: Review and sign the [Code of Business Conduct & Ethics Acknowledgment Form](https://about.gitlab.com/handbook/people-operations/code-of-conduct/#code-of-business-conduct--ethics-acknowledgment-form). This document was sent to your GitLab email inbox from BambooHR requesting your signature. Please comment in this issue and ping your assigned People Experience team member if you have not received it.
......
......@@ -20,7 +20,7 @@
1. [ ] Join Slack channels: #finance, #business-technology, #bt-team-lounge.
* [ ] If you are a BSA: #bt-business-engagement. You can reach out in #bt-business-engagement to the other BSAs to ask which channels you should join based on your area of focus
* [ ] If you are part of the Data Team: #data, #data-lounge. Find other channels to join in the [Data Handbook](https://about.gitlab.com/handbook/business-ops/data-team/#slack).
* [ ] If you are part of the Data Team: #data, #data-lounge. Find other channels to join in the [Data Handbook](https://about.gitlab.com/handbook/business-technology/data-team/#slack).
* [ ] If you are part of the IT Team: #it_help. Ask your manager to invite you to any private channels.
* [ ] If you are part of the Procurement team: #procurement
......
......@@ -73,8 +73,8 @@
1. [ ] New team member: Consider joining the #data channel on Slack, as it's the best place to reach out to the data team.
1. [ ] New team member: Consider joining the #data-lounge channel on Slack, as it's where data-related resources get shared.
1. [ ] New team member: The data team project can be found at gitlab.com/gitlab-data/analytics. If you have data requests, be sure to create issues there.
1. [ ] New team member: Review the [Data for Product Managers](https://about.gitlab.com/handbook/business-ops/data-team/data-for-product-managers/) page in the handbook.
1. [ ] New team member: There is a lot more information on data at GitLab in the [Data Team Handbook](https://about.gitlab.com/handbook/business-ops/data-team/#data-team-handbook)
1. [ ] New team member: Review the [Data for Product Managers](https://about.gitlab.com/handbook/business-technology/data-team/data-for-product-managers/) page in the handbook.
1. [ ] New team member: There is a lot more information on data at GitLab in the [Data Team Handbook](https://about.gitlab.com/handbook/business-technology/data-team/#data-team-handbook)
- [ ] New team member: Watch ["The State of Product Data"](https://www.youtube.com/watch?v=eNLkj3Ho2bk&feature=youtu.be) from Eli Kastelein at the Growth Fastboot. (You'll need to be logged into GitLab Unfiltered.)
</details>
......@@ -85,7 +85,7 @@
<summary>New Team Member</summary>
Sisense (formerly Periscope) is GitLab's data analysis and business intelligence tool. You may see Sisense referred to as Periscope as their [name change is in progress](https://www.sisense.com/press-release/sisense-acquisition-of-periscope-yields-versatile-bi-platform/). Confirm you can access. This should have been part of your [access request issue](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/blob/master/.gitlab/issue_templates/role_baseline_access_request_tasks/department_product_management/role_product_manager.md).
1. [ ] New team member: Obtain access to [Periscope](https://about.gitlab.com/handbook/business-ops/data-team/periscope/), our data analysis tool.
1. [ ] New team member: Obtain access to [Periscope](https://about.gitlab.com/handbook/business-technology/data-team/periscope/), our data analysis tool.
1. [ ] Review the [getting started with Periscope Data guide](https://doc.periscopedata.com/article/getting-started)
1. [ ] Familiarize yourself with relevant [dashboards](https://app.periscopedata.com/app/gitlab/topic/Product/ab707846c91f4d30b1c1ca0399803d67).
......@@ -113,7 +113,7 @@ This data comes from the usage ping that comes with a GitLab installation.
[Snowplow](https://snowplowanalytics.com) is an open source web analytics collector.
1. [ ] New team member: To understand how this is implemented at GitLab read [Feature Implementation](https://about.gitlab.com/handbook/product/feature-instrumentation/#instrumentation-for-gitlabcom).
1. [ ] New team member: Also read how we pull data from [S3 into Snowflake](https://about.gitlab.com/handbook/business-ops/data-team/#snowplow-infrastructure)
1. [ ] New team member: Also read how we pull data from [S3 into Snowflake](https://about.gitlab.com/handbook/business-technology/data-team/#snowplow-infrastructure)
1. [ ] New team member: Familiarize yourself with the [Snowplow Open Source documentation](https://github.com/snowplow/snowplow).
1. [ ] New team member: We use the [Snowplow dbt package](https://hub.getdbt.com/fishtown-analytics/snowplow/latest/) on our models. Their documentation does show up in our dbt docs.
......
......@@ -11,7 +11,7 @@ Thank you for reaching out, the team member you are trying to contact is no long
3. ces@gitlab.com - For candidate-related queries
4. accountingops@gitlab.com - For accounting-related queries
5. finance@gitlab.com For finance-related queries
6. peopleops@gitlab.com - For business operations, legal and general people ops assistance or if unsure of which category to choose
6. peopleops@gitlab.com - For Business Technology, legal and general people ops assistance or if unsure of which category to choose
If the issue is sensitive and you would prefer to reach out to an individual, please email the closest group and request to be redirected to the best person to contact.
......
......@@ -175,7 +175,7 @@
<tr>
<td align="left" style="font-size:0px;padding:10px 25px;word-break:break-word;">
<div style="font-family:Ubuntu, Helvetica, Arial, sans-serif;font-size:14px;line-height:1;text-align:left;color:#000000;">Okta is our identity and authentication portal, which you will use to access most of your cloud-based applications, including your GitLab email account. You should have received an invitation email from GitLab about Okta within the
last day. Please follow the instructions in that email to activate your account. For further information about how GitLab uses Okta, please check out the <a href='https://about.gitlab.com/handbook/business-ops/okta/'>handbook page</a>.</div>
last day. Please follow the instructions in that email to activate your account. For further information about how GitLab uses Okta, please check out the <a href='https://about.gitlab.com/handbook/business-technology/okta/'>handbook page</a>.</div>
</td>
</tr>
<tr>
......
......@@ -4,7 +4,7 @@ Welcome to GitLab! We're so excited that you've joined our team!
To ensure the seamless setup of your work accounts, please log out from any personal Gsuite/Gmail and GitLab.com accounts before beginning any of the below steps.
<b>Okta</b> is our identity and authentication portal, which you will use to access most of your cloud-based applications. You should have received an invitation email from GitLab about Okta, and please follow the instructions in that email to activate your account. For further information about how GitLab uses Okta,<a href='https://about.gitlab.com/handbook/business-ops/okta'>please check out the handbook page</a>.
<b>Okta</b> is our identity and authentication portal, which you will use to access most of your cloud-based applications. You should have received an invitation email from GitLab about Okta, and please follow the instructions in that email to activate your account. For further information about how GitLab uses Okta,<a href='https://about.gitlab.com/handbook/business-technology/okta'>please check out the handbook page</a>.
(If you can't find the Okta activation email, please firstly check your Spam/Junk Folders or other folders in case your email client has filed it somewhere. The IT Ops team can assist if you are unable to find it or if the token has expired. Please email itops@gitlab.com, and cc people-exp@gitlab.com for visibility.)
To be as helpful as possible, we created the following <a href='https://www.youtube.com/watch?v=Y5lev17qXbw&feature=youtu.be'>video</a> to help you understand how to start your onboarding process. Please make sure to create a new GitLab.com account dedicated for your work at GitLab. It's important to keep this new account separate from any personal projects or engagements as this new account will be disabled on leaving GitLab. <b>Please ensure not to use Okta or GoogleSSO to create a GitLab account</b>, the account will not have the correct permission level to get into your onboarding issue.
......
......@@ -23,7 +23,7 @@
</mj-text>
<mj-text font-size="14px">
Okta is our identity and authentication portal, which you will use to access most of your cloud-based applications, including your GitLab email account. You should have received an invitation email from GitLab about Okta within the last day. Please follow the instructions in that email to activate your account. For further information about how GitLab uses Okta, please check out the <a href='https://about.gitlab.com/handbook/business-ops/okta/'>handbook page</a>.
Okta is our identity and authentication portal, which you will use to access most of your cloud-based applications, including your GitLab email account. You should have received an invitation email from GitLab about Okta within the last day. Please follow the instructions in that email to activate your account. For further information about how GitLab uses Okta, please check out the <a href='https://about.gitlab.com/handbook/business-technology/okta/'>handbook page</a>.
</mj-text>
<mj-text>
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment