Commit acffa71b authored by Lis Vinueza's avatar Lis Vinueza 🌸

fix name

parent 43e3c13c
Pipeline #170599833 skipped with stage
......@@ -43,7 +43,7 @@
/sites/handbook/source/handbook/business-ops/data-team/learning-library/ @gitlab-data
/sites/handbook/source/handbook/business-ops/data-team/kpi-index/ @kathleentam @jjstark
/sites/handbook/source/handbook/business-ops/data-team/programs/data-for-product-managers/ @mpeychet @kathleentam
/sites/handbook/source/handbook/business-ops/employee-enablement/ @pkaldis
/sites/handbook/source/handbook/business-ops/team-member-enablement/ @pkaldis
/sites/handbook/source/handbook/business-ops/enterprise-applications/ @bryanwise @ccnelson
sites/handbook/source/handbook/business-ops/enterprise-applications/architecture @j.carey @bryanwise @ccnelson
sites/handbook/source/handbook/business-ops/enterprise-applications/portal @j.carey @bryanwise @ccnelson
......
......@@ -51,7 +51,7 @@ A full list of packages available are on the [dbt Hub site](https://hub.getdbt.c
If you're interested in using dbt, the [dbt documemtation has a great tutorial](https://tutorial.getdbt.com/tutorial/setting-up/) on getting setup to work on data from a fictional business called Jaffle Shop.
If you wish to use dbt and contribute to the data team project, you'll need to gain access to our Snowflake instance, which can be done via an [access request](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/).
If you wish to use dbt and contribute to the data team project, you'll need to gain access to our Snowflake instance, which can be done via an [access request](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/).
### Configuration
......
......@@ -68,7 +68,7 @@ We have high level views of the enterprise application ecosystem and can help tr
<a href="https://gitlab.com/groups/gitlab-com/-/boards/1596495?assignee_username=lisvinueza&" class="btn btn-purple">Work Management Board</a>
* Partner to Employee Enablement and People Operations
* Partner to Team Member Enablement and People Operations
* Business Technology Operations and Workflows
## <i class="fas fa-user-shield" id="biz-tech-icons"></i> IT Compliance Manager
......
......@@ -18,8 +18,8 @@ description: "Business Operations"
<div class="flex-row" markdown="0">
<div>
<h5>Employment Enablement</h5>
<a href="https://about.gitlab.com/handbook/business-ops/employee-enablement/" class="btn btn-purple" style="width:170px;margin:5px;">Handbook page</a>
<a href="https://about.gitlab.com/handbook/business-ops/employee-enablement/#welcome-to-the-business-technology-employee-enablement-teamit-handbook-page" class="btn btn-purple" style="width:170px;margin:5px;">Contact the team</a>
<a href="https://about.gitlab.com/handbook/business-ops/team-member-enablement/" class="btn btn-purple" style="width:170px;margin:5px;">Handbook page</a>
<a href="https://about.gitlab.com/handbook/business-ops/team-member-enablement/#welcome-to-the-business-technology-employee-enablement-teamit-handbook-page" class="btn btn-purple" style="width:170px;margin:5px;">Contact the team</a>
</div>
<div>
<h5>Enterprise Applications</h5>
......
......@@ -93,7 +93,7 @@ As a precaution, you will also need to change your Okta Password.
Create a [new application setup issue](https://gitlab.com/gitlab-com/gl-security/zero-trust/okta/issues/new?issuable_template=okta_add_application) and fill in as much information as you can.
Okta is currently configured with assigned groups/roles based on a team member's role/group.
Refer to the [Access Removal Request](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/#access-change-request) section of the handbook for additional information on why an application may not be available in Okta.
Refer to the [Access Removal Request](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/#access-change-request) section of the handbook for additional information on why an application may not be available in Okta.
### How do I get my application set up within Okta?
......
---
layout: handbook-page-toc
title: "Employee Enablement Team"
title: "Team Member Enablement"
---
<link rel="stylesheet" type="text/css" href="/stylesheets/biztech.css" />
......@@ -13,7 +13,7 @@ title: "Employee Enablement Team"
## <i class="far fa-paper-plane" id="biz-tech-icons"></i> How to reach out to us?
<div class="flex-row" markdown="0" style="height:100px;justify-content:flex-start;">
<a href="https://gitlab.com/gitlab-com/business-ops/employee-enablement/issue-tracker/-/issues/new" class="btn btn-purple-inv" style="width:170px;margin:5px;height:100%;display:flex;align-items:center;justify-content:center;">Open an issue</a>
<a href="https://gitlab.com/gitlab-com/business-ops/team-member-enablement/issue-tracker/-/issues/new" class="btn btn-purple-inv" style="width:170px;margin:5px;height:100%;display:flex;align-items:center;justify-content:center;">Open an issue</a>
<a href="https://gitlab.slack.com/archives/CK4EQH50E" class="btn btn-purple-inv" style="width:170px;margin:5px;height:100%;display: flex;align-items:center;justify-content:center;">#it-help in slack</a>
<a href="https://www.worldtimebuddy.com/?pl=1&lid=4143861,4726206,2964574,2158177&h=4143861" class="btn btn-purple-inv" style="width:170px;margin:5px;height:100%;display: flex;align-items:center;justify-content:center;">What timezone are we located in?</a>
</div>
......@@ -25,12 +25,12 @@ title: "Employee Enablement Team"
#### Access Requests
* For information about the access request policies and security guidelines, please refer to the Security Team's [access request handbook page section](/handbook/engineering/security/#access-management-process).
* For links to role based access request templates, system access templates, and other general instructions and FAQs, please refer to the [Access Requests page](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests).
* For links to role based access request templates, system access templates, and other general instructions and FAQs, please refer to the [Access Requests page](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests).
#### Baseline & Role-Based Entitlements
* For information about baseline entitlements and role-based access, please refer to the [baseline entitlements handbook page](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/baseline-entitlements).
* For information on how to create a Role-Based Entitlement, please refer to the [instructions on how to create role-based entitlements](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/baseline-entitlements#how-do-i-create-a-role-based-entitlement-template).
* For information about baseline entitlements and role-based access, please refer to the [baseline entitlements handbook page](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/baseline-entitlements).
* For information on how to create a Role-Based Entitlement, please refer to the [instructions on how to create role-based entitlements](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/baseline-entitlements#how-do-i-create-a-role-based-entitlement-template).
#### Automated Group Membership Reports for Managers
......@@ -45,11 +45,11 @@ To read more about Okta, please visit the [**Okta**](/handbook/business-ops/okta
#### GitLab Onboarding and machine management
Please visit the GitLab Onboarding and machine management [handbook page](/handbook/business-ops/employee-enablement/onboarding-access-requests/)
Please visit the GitLab Onboarding and machine management [handbook page](/handbook/business-ops/team-member-enablement/onboarding-access-requests/)
#### Self-help and troubleshooting
Experiencing some issues with your machine, access to systems, 2FA or other IT related issues? Please visit our [self-help and troubleshooting handbook page](/handbook/business-ops/employee-enablement/self-help-troubleshooting)
Experiencing some issues with your machine, access to systems, 2FA or other IT related issues? Please visit our [self-help and troubleshooting handbook page](/handbook/business-ops/team-member-enablement/self-help-troubleshooting)
## <i class="fas fa-rocket" id="biz-tech-icons"></i> Mission Statement
......
......@@ -159,7 +159,7 @@ Once a Role Based Entitlement template has been created and approved by all auth
#### Role Based Entitlements - information for managers
Role based entitlements are pre-defined groups and system-level access that are granted automatically to team members depending on their role. Role based entitlements Access Requests are created automatically for a new team member on their second day at GitLab ***if*** a template exists for their role. We recommend creating a template for all the roles that you are currently hiring for so the new team member's onboarding is as smooth as possible. You can create a new template for any role following [these instructions](https://about.gitlab.com/handbook/business-ops/employee-enablement/it-ops-team/access-requests/#how-to-create-role-based-entitlement-templates). These templates need to include the tools/systems that all people in a role should get access to and nothing should be added/removed when creating a new issue.
Role based entitlements are pre-defined groups and system-level access that are granted automatically to team members depending on their role. Role based entitlements Access Requests are created automatically for a new team member on their second day at GitLab ***if*** a template exists for their role. We recommend creating a template for all the roles that you are currently hiring for so the new team member's onboarding is as smooth as possible. You can create a new template for any role following [these instructions](https://about.gitlab.com/handbook/business-ops/team-member-enablement/it-ops-team/access-requests/#how-to-create-role-based-entitlement-templates). These templates need to include the tools/systems that all people in a role should get access to and nothing should be added/removed when creating a new issue.
If you haven't created a role based entitlement template for a role you are hiring for, you'll need to manually create a [Single Person Access Request](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/issues/new?issuable_template=Single_Person_Access_Request) for your new hire.
......
......@@ -18,7 +18,7 @@ title: "Access Requests (AR) FAQs"
## I need access!
#### My AR request has been open for a while, how can I get traction on it?
1. Review that the access request has been completed according to the [instructions](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests#how-do-i-choose-which-template-to-use) and that you have included the system/vault/group/project you need access to plus the role or permissions needed.
1. Review that the access request has been completed according to the [instructions](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests#how-do-i-choose-which-template-to-use) and that you have included the system/vault/group/project you need access to plus the role or permissions needed.
1. Most access requests need Manager approval so make sure to tag your manager in the AR and ask them to add the ~"AR-Approval::Manager Approved" and ~"ReadyForProvisioning" labels to the issue
1. Make sure you have tagged and assigned the issue to the correct provisioner(s) for the tool(s) you are requesting access to. You can find the provisioners for all our tools in our [Tech Stack](https://docs.google.com/spreadsheets/d/1mTNZHsK3TWzQdeFqkITKA0pHADjuurv37XMuHv12hDU/edit#gid=0)
1. If the provisioner is the IT team, please make sure to add the ~"IT::to do" label to the AR.
......
......@@ -19,8 +19,8 @@ If you have any access requests related questions, please reach out to #it_help
<div class="flex-row" markdown="0">
<div>
<a href="/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/frequently-asked-questions" class="btn btn-purple" style="width:170px;margin:5px;">Frequently asked questions</a>
<a href="/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/baseline-entitlements" class="btn btn-purple" style="width:170px;margin:5px;">Baseline Entitlements</a>
<a href="/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/frequently-asked-questions" class="btn btn-purple" style="width:170px;margin:5px;">Frequently asked questions</a>
<a href="/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/baseline-entitlements" class="btn btn-purple" style="width:170px;margin:5px;">Baseline Entitlements</a>
</div>
</div>
......@@ -205,7 +205,7 @@ Every review should include a [least privilege review](/handbook/engineering/sec
##### Department Access Request Boards
* If you need additional labels or have suggestions for improving the process until we can fully automate, please [open an issue](https://gitlab.com/gitlab-com/business-ops/employee-enablement/issue-tracker/-/issues/new).
* If you need additional labels or have suggestions for improving the process until we can fully automate, please [open an issue](https://gitlab.com/gitlab-com/business-ops/team-member-enablement/issue-tracker/-/issues/new).
* ARs are auto-assigned and auto-labeled when possible by department. In some cases, there are multiple provisioners per tool. If a template cannot be auto-assigned, Business Operations will provide a board where the provisioners can review their department's issues by label (ie `dept::to do`. It is up to the department to manage the workflow on who works the issues to completion.
* **Moving an issue from one column to another will remove the first label (per the column header) and add the second label. Please use caution when moving issues between columns.**
* Departments can check their outstanding access request issues by viewing their board below.
......
......@@ -160,19 +160,19 @@ In other words, we eliminate this possibility of becoming a situation to be mana
##### Logistics needs
To be able to use a laptop vendor, we have to be able to purchase and ship hardware to our team members regardless of where they live.
Therefore the vendor should be able to handle most if not all shipping requirements to all team members. Our current hardware provider for US and most international locations is CDW. GitLab laptops that are procured from CDW will come with GitLab branded asset labels by default. Please refer to this issue for more information on GitLab asset labels. [GitLab Branded Laptop Labels](https://gitlab.com/gitlab-com/business-ops/employee-enablement/it-ops-issue-tracker/-/issues/352)
Therefore the vendor should be able to handle most if not all shipping requirements to all team members. Our current hardware provider for US and most international locations is CDW. GitLab laptops that are procured from CDW will come with GitLab branded asset labels by default. Please refer to this issue for more information on GitLab asset labels. [GitLab Branded Laptop Labels](https://gitlab.com/gitlab-com/business-ops/team-member-enablement/it-ops-issue-tracker/-/issues/352)
### Laptop Refresh
Team member Laptops can be refreshed after 3 years (of use!) without question. However, if the replacement laptop is outside the standardized specifications listed [here](/handbook/business-ops/employee-enablement/onboarding-access-requests/#apple-hardware) than manager approval will be required before IT can purchase the replacement laptop.
Team member Laptops can be refreshed after 3 years (of use!) without question. However, if the replacement laptop is outside the standardized specifications listed [here](/handbook/business-ops/team-member-enablement/onboarding-access-requests/#apple-hardware) than manager approval will be required before IT can purchase the replacement laptop.
If you feel you need a new laptop to be effective at your job before then, reach out to IT and your manager.
Replacement laptops for broken GitLab laptops can be purchased as needed by [creating an issue](https://gitlab.com/gitlab-com/business-ops/employee-enablement/issue-tracker/-/issues/new?issuable_template=Laptop_Replacement) in the Employee Enablement issue tracker project. Laptops ordered as part of the refresh program use the same template.
Replacement laptops for broken GitLab laptops can be purchased as needed by [creating an issue](https://gitlab.com/gitlab-com/business-ops/team-member-enablement/issue-tracker/-/issues/new?issuable_template=Laptop_Replacement) in the Team member Enablement issue tracker project. Laptops ordered as part of the refresh program use the same template.
This process can also be followed for laptops that are not broken but old enough that you are having trouble completing your work.
Please refer to the [spirit of spending company money](/handbook/spending-company-money/) when deciding whether or not it is appropriate to replace your functioning laptop.
Everyone's needs are different so it is hard to set a clear timeline of when computer upgrades are necessary for all team-members, but team-members become eligible for an updated laptop after 3 years.
If you qualify/complete a laptop refresh, please also refer to our [Laptop Buy back Policy](/handbook/business-ops/employee-enablement/onboarding-access-requests/#laptop-buy-back-policy) below.
If you qualify/complete a laptop refresh, please also refer to our [Laptop Buy back Policy](/handbook/business-ops/team-member-enablement/onboarding-access-requests/#laptop-buy-back-policy) below.
Many team members can use their company issued laptop until it breaks.
If your productivity is suffering, you can request a new laptop.
......@@ -202,9 +202,9 @@ Please check with the IT Ops department if you have any questions.
If your laptop is broken and needs to be repaired you can take it into an Apple repair store.
If the repair is not going to be too expensive (more than $1000 dollars USD), go ahead and repair and expense.
If the repair is going to take longer than a day then you need to make sure you have a back up laptop to work on that is non-Windows.
You can open an issue in the [Employee Enablement Issue Tracker](https://gitlab.com/gitlab-com/business-ops/employee-enablement/issue-tracker/-/issues/new?issuable_template=Laptop_Repair) to document the repair and get your managers approval.
You can open an issue in the [Team Member Enablement Issue Tracker](https://gitlab.com/gitlab-com/business-ops/team-member-enablement/issue-tracker/-/issues/new?issuable_template=Laptop_Repair) to document the repair and get your managers approval.
If, however, the repair is going to be expensive and take weeks to fix and you have no back up laptop, your best option is to replace the laptop.
In this case please open [an issue to replace](https://gitlab.com/gitlab-com/business-ops/employee-enablement/issue-tracker/-/issues/new?issuable_template=Laptop_Replacement).
In this case please open [an issue to replace](https://gitlab.com/gitlab-com/business-ops/team-member-enablement/issue-tracker/-/issues/new?issuable_template=Laptop_Replacement).
Then please follow the guidelines in the template and once you receive the new laptop we can have the old one sent off to our reseller.
### Configuring New Laptops & Apple IDs
......@@ -293,7 +293,7 @@ GitLab has a large and ever-growing fleet of laptops, which IT Operations is res
In order to do this and combined with our Zero Trust security policies and various Compliance needs, there must be some measure of intelligence and reporting in place.
To accomplish this goal we are utilizing JAMF for MAC devices to obtain only the essential information required. For Linux machines we will be utilizing DriveStrike as a light-touch mechanism.
For more information regarding JAMF, refer to our [Endpoint Management](/handbook/business-ops/employee-enablement/onboarding-access-requests/endpoint-management/) handbook page.
For more information regarding JAMF, refer to our [Endpoint Management](/handbook/business-ops/team-member-enablement/onboarding-access-requests/endpoint-management/) handbook page.
**DriveStrike**
......
......@@ -45,7 +45,7 @@ A lot of people coming onboard to GitLab have had some sort of exposure to macOS
### How to Erase a Disk for Mac
If you are keeping your GitLab machine [Laptop Buy Back Policy](/handbook/business-ops/employee-enablement/onboarding-access-requests/#laptop-buy-back-policy) it is required you wipe the machine and restore to base OS, these instructions will help you accomplish this.
If you are keeping your GitLab machine [Laptop Buy Back Policy](/handbook/business-ops/team-member-enablement/onboarding-access-requests/#laptop-buy-back-policy) it is required you wipe the machine and restore to base OS, these instructions will help you accomplish this.
[How to erase a disk](https://support.apple.com/en-us/HT208496)
......@@ -127,7 +127,7 @@ This usually occurs when the emails you send out get reported for spam. Collect
**How do I get access to my account after suspension?**
Someone from IT will need to unlock your account. Please submit a [Employee Enablement request](https://gitlab.com/gitlab-com/business-ops/employee-enablement/issue-tracker/-/issues/new?issuable_template=General%20HelpDesk%20Request) or reach out to us on the #it-help slack channel.
Someone from IT will need to unlock your account. Please submit a [Team Member Enablement request](https://gitlab.com/gitlab-com/business-ops/team-member-enablement/issue-tracker/-/issues/new?issuable_template=General%20HelpDesk%20Request) or reach out to us on the #it-help slack channel.
**How do I prevent this from happening?**
......@@ -144,7 +144,7 @@ Great! If you are getting a new phone, and are aware of when you'll receive it.
It's handy to advise us firstly, so we can reset your MFA and your new device can authenticate for accounts straight away.
Please fill out the issue below and we'll reset as soon as we can.
Access request for OKTA MFA [here](https://gitlab.com/gitlab-com/business-ops/employee-enablement/issue-tracker/-/issues/new?issuable_template=General%20HelpDesk%20Request).
Access request for OKTA MFA [here](https://gitlab.com/gitlab-com/business-ops/team-member-enablement/issue-tracker/-/issues/new?issuable_template=General%20HelpDesk%20Request).
### Questions about Okta?
......@@ -159,11 +159,11 @@ Our security team also did an amazing write-up for Linux installations - [Linux
## Can't find what you are looking for?
Request for support should have an issue open at [IT Help Issues](https://gitlab.com/gitlab-com/business-ops/employee-enablement/issue-tracker/-/issues/new?issuable_template=General%20HelpDesk%20Request).
Request for support should have an issue open at [IT Help Issues](https://gitlab.com/gitlab-com/business-ops/team-member-enablement/issue-tracker/-/issues/new?issuable_template=General%20HelpDesk%20Request).
### How to Contact Us or Escalate Priority Issues Outside of Standard Hours
We ask that all requests are made through an [IT Help Issue](https://gitlab.com/gitlab-com/business-ops/employee-enablement/issue-tracker/-/issues/new?issuable_template=General%20HelpDesk%20Request). We will triage and address them as soon as we can. All issues created in the queue are public by default. Privileged or private communications should be sent to it-help@gitlab.com. Screenshots and videos are very helpful when experiencing an issue, especially if there is an error message.
We ask that all requests are made through an [IT Help Issue](https://gitlab.com/gitlab-com/business-ops/team-member-enablement/issue-tracker/-/issues/new?issuable_template=General%20HelpDesk%20Request). We will triage and address them as soon as we can. All issues created in the queue are public by default. Privileged or private communications should be sent to it-help@gitlab.com. Screenshots and videos are very helpful when experiencing an issue, especially if there is an error message.
As a distributed team, we have support around the clock with team members in North America, Europe and Australia.
High volumes of issues being triaged can dictate the delay in response within that window. If the issue is extremely time sensitive and warrants escalation, use judgement on whether or not it can wait until ‘business hours’.
......
......@@ -28,7 +28,7 @@ System owners will remain the point of contact for provisioning and issues invol
- Do you need to update a column in tech stack Google sheet? [Submit an issue.](https://gitlab.com/gitlab-com/business-ops/Business-Operations/issues/new?issuable_template=Update%20Tech%20Stack%20Information)
- Do you need to add a new tool to the tech stack Google sheet? [Submit an issue.](https://gitlab.com/gitlab-com/business-ops/Business-Operations/issues/new?issuable_template=Add%20New%20System%20to%20Tech%20Stack%20Application%20List)
- Do you need to change who is a provisioner to an application? [Submit an issue.](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/issues/new?issuable_template=Update_Tech_Stack_Provisioner)
- Do you need access to an application in the tech stack? Check out [the handbook page](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/) for a list of the templates you can use to request access.
- Do you need access to an application in the tech stack? Check out [the handbook page](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/) for a list of the templates you can use to request access.
- Need help with an application? Reach out in the slack channel named in the [Tech Stack google sheet column G](https://docs.google.com/spreadsheets/d/1mTNZHsK3TWzQdeFqkITKA0pHADjuurv37XMuHv12hDU/edit#gid=0) for the application you need help with.
- Do you want to buy a new application? Check out [the handbook page](/handbook/finance/procure-to-pay/#procure-to-pay-process) on the process. Tools may not be integrated into the tech stack without following the process.
......
......@@ -11,7 +11,7 @@ title: "Business Operations - Tech Stack Details"
## Request Access
If you need to request access for any of the following tools, please refer to and follow the [Access Request process](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/frequently-asked-questions/#so-you-need-access-to-a-system-or-a-groupvault).
If you need to request access for any of the following tools, please refer to and follow the [Access Request process](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/frequently-asked-questions/#so-you-need-access-to-a-system-or-a-groupvault).
## 1Password
[1Password](https://1password.com/) is a password manager. GitLab uses 1Passwords for Teams which is a hosted service. Please refer to the [1Password Guide](/handbook/security/#1password-guide) for additional information.
......
......@@ -43,7 +43,7 @@ To raise an issue with a specific team, please use below most commonly used chan
### Channel Categories
#### Account Channels (a_)
These channels (prefixed with a `a_`) are for team members to collaborate and communicate regarding the account for a customer organization. In some cases, they are marked as private or we are connected to customer's own Slack workspace using Shared Channels. To request a new channel or to make changes to existing channels, please use the [access request process](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/#slack-google-groups-1password-vaults-or-groups-access-requests).
These channels (prefixed with a `a_`) are for team members to collaborate and communicate regarding the account for a customer organization. In some cases, they are marked as private or we are connected to customer's own Slack workspace using Shared Channels. To request a new channel or to make changes to existing channels, please use the [access request process](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/#slack-google-groups-1password-vaults-or-groups-access-requests).
Many customers that require coordination across GitLab teams have dedicated channels in slack to discuss that customer's needs internally. Those channels are all postfixed with `-internal`.
......
......@@ -156,7 +156,7 @@ When the demo systems team was established in October 2019, we created a prelimi
</tr>
<tr>
<td>FY21-Q2</td>
<td><a href="https://gitlab.com/gitlab-com/customer-success/demo-systems/demo-feature-requests/demosys-okrs/-/issues/7">demosys-okrs#7</a> <a href="https://gitlab.com/gitlab-com/business-ops/employee-enablement/it-ops-issue-tracker/-/issues/301">it-ops#301</a></td>
<td><a href="https://gitlab.com/gitlab-com/customer-success/demo-systems/demo-feature-requests/demosys-okrs/-/issues/7">demosys-okrs#7</a> <a href="https://gitlab.com/gitlab-com/business-ops/team-member-enablement/it-ops-issue-tracker/-/issues/301">it-ops#301</a></td>
<td>Transition AWS `gitlab-np` account to new IT Ops AWS account</td>
</tr>
<tr>
......
......@@ -44,7 +44,7 @@ If you are logging in through Salesforce, you can also quickly open the Salesfor
To access Gainsight directly, go to [gitlab.gainsightcloud.com](https://gitlab.gainsightcloud.com/) and when prompted for your username and password, enter _only_ your GitLab email address. As soon as it is entered, the screen should change to indicate that you are using single sign-on, and when you click "log in" it will redirect you to Okta.
- If you need to request access to Gainsight, fill out an [Access Request](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/#single-person-access-request) and have your manager add the manager approved label.
- If you need to request access to Gainsight, fill out an [Access Request](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/#single-person-access-request) and have your manager add the manager approved label.
- If you need help locating the Gainsight NXT tab in Salesforce or the Gainsight Okta tile, submit an issue using the [Gainsight Request Template](https://gitlab.com/gitlab-com/sales-team/field-operations/sales-operations/-/issues/new?issue%5Bassignee_id%5D=&issue%5Bmilestone_id%5D=).
### Confirm your timezone
......
......@@ -20,7 +20,7 @@ The [access request project](https://gitlab.com/gitlab-com/team-member-epics/acc
3. [Access Reviews](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/issues/new?issuable_template=Access_Review)
4. [New Service Account Requests](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/issues/new?issuable_template=New_Service_Account_Request)
Usage guidelines for each of the access templates is outlined on the [Employee enablement's handbook page](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/).
Usage guidelines for each of the access templates is outlined on the [Team Member enablement's handbook page](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/).
These templates should be used during the [onboarding process](/handbook/people-group/general-onboarding/) and throughout the employment tenure of a GitLabber. Access required as part of the team member's onboarding should be requested using the [New Access Requests](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/issues/new?issuable_template=Single_Person_Access_Request) or if applicable, one of the available [Role-based entitlements templates](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/tree/master/.gitlab/issue_templates/role_baseline_access_request_tasks).
......
......@@ -74,7 +74,7 @@ The following requirements are driven by 3 high level guidelines:
### Service Account usage
1. Service accounts names SHOULD be meaningful.
1. Service accounts with access to RED data MUST follow the [Access Request](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/#shared-account-access-request)
1. Service accounts with access to RED data MUST follow the [Access Request](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/#shared-account-access-request)
process.
1. Service accounts with access to RED data MUST be limited to single logical scope; for example, a single GCP project.
......
......@@ -30,7 +30,7 @@ The idea behind stable counterparts is articulated best in [related infrastructu
| [SecOps](/handbook/engineering/security/operations/) | [@lcoleman](https://gitlab.com/lcoleman) |
| [AppSec](/handbook/engineering/security/application-security/) | [@twsilveira](https://gitlab.com/twsilveira) |
| [BizOps](/handbook/business-ops/) | [@uswaminathan](https://gitlab.com/uswaminathan) |
| [Employee Enablement](/handbook/business-ops/employee-enablement/) | [@uswaminathan](https://gitlab.com/uswaminathan) |
| [Team Member Enablement](/handbook/business-ops/team-member-enablement/) | [@uswaminathan](https://gitlab.com/uswaminathan) |
| [Internal Audit](/handbook/internal-audit/) | [@twsilveira](https://gitlab.com/twsilveira) |
| [Data Team](/handbook/business-ops/data-team/) | [@sttruong](https://gitlab.com/sttruong) |
| [People team](/handbook/people-group/) | [@jblanco2](https://gitlab.com/jblanco2) |
......
......@@ -49,7 +49,7 @@ Examples of evidence an auditor might request to satisfy this control:
### Policy Reference
* [Laptop or Desktop System configuration](https://about.gitlab.com/handbook/security/#laptop-or-desktop-system-configuration)
* [Configuring New Laptops](/handbook/business-ops/employee-enablement/onboarding-access-requests/#configuring-new-laptops--apple-ids)
* [Configuring New Laptops](/handbook/business-ops/team-member-enablement/onboarding-access-requests/#configuring-new-laptops--apple-ids)
* [Security Best Practices](https://about.gitlab.com/handbook/security/#best-practices)
## Framework Mapping
......
......@@ -39,9 +39,9 @@ Non-public information relating to this security control as well as links to the
- [Access Control Policy](/handbook/engineering/security/Access-Management-Policy.html)
- [Access Request Process](/handbook/engineering/security/Access-Management-Policy.html#access-requests-and-onboarding)
- [Principle of least privilege access](/handbook/engineering/security/Access-Management-Policy.html#principle-of-least-privilege)
- [IT Ops instructions and FAQs for Access Requests](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/)
- [IT Ops instructions and FAQs for Access Requests](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/)
- [Okta Baseline Entitlements-Okta Application stack](/handbook/business-ops/okta/okta-appstack/)
- [Single Person Access Requests](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/#single-person-access-request)
- [Single Person Access Requests](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/#single-person-access-request)
- [Access Request Template](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/issues/new?issuable_template=New_Access_Request)
- [Template used for Access Reviews](https://gitlab.com/gitlab-com/team-member-epics/access-requests/issues/new?issuable_template=Access_Review)
......
......@@ -36,7 +36,7 @@ Non-public information relating to this security control as well as links to the
- [Access Reviews](https://about.gitlab.com/handbook/engineering/security/#access-reviews)
- [Access Control Policy and Procedures](https://about.gitlab.com/handbook/engineering/security/#access-control-policy-and-procedures)
- [Job Transfers](https://about.gitlab.com/handbook/engineering/security/#job-transfers)
- [Access Change Request](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/#access-change-request)
- [Access Change Request](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/#access-change-request)
- [Access Removal Request](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/tree/master)
## Framework Mapping
......
......@@ -61,11 +61,11 @@ Examples of evidence an auditor might request to satisfy this control:
### Policy Reference
- [Shared Account Access Request](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/#shared-account-access-request)
- [Shared Account Access Request](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/#shared-account-access-request)
- [Access Control Policy and Procedures](https://about.gitlab.com/handbook/engineering/security/#access-control-policy-and-procedures)
- [Okta documentation on shared accounts](https://about.gitlab.com/handbook/business-ops/okta/#i-have-an-application-that-uses-a-shared-password-for-my-team-can-i-move-this-to-okta)
- [New Shared Account Access Request](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/#shared-account-access-request)
- [Shared Account Access Request Handbook page](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/)
- [New Shared Account Access Request](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/#shared-account-access-request)
- [Shared Account Access Request Handbook page](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/)
## Framework Mapping
* PCI
......
......@@ -39,7 +39,7 @@ Non-public information relating to this security control as well as links to the
- [Access Reviews](https://about.gitlab.com/handbook/engineering/security/#access-reviews)
- [Access Control Policy and Procedures](https://about.gitlab.com/handbook/engineering/security/#access-control-policy-and-procedures)
- [Job Transfers](https://about.gitlab.com/handbook/engineering/security/#job-transfers)
- [Access Change Request](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/#access-change-request)
- [Access Change Request](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/#access-change-request)
- [Access Removal Request](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/tree/master)
......
......@@ -70,9 +70,9 @@ Non-public information relating to this security control as well as links to the
- [GitLab Security Practices](https://about.gitlab.com/handbook/security/)
- [Business Continuity Plan](https://about.gitlab.com/handbook/business-ops/gitlab-business-continuity-plan.html)
- [Data Team](https://about.gitlab.com/handbook/business-ops/data-team/) Policies and Standards
- [Employee Enablement Policies and Standards](/handbook/business-ops/employee-enablement/onboarding-access-requests/)
- [Inventory Management](/handbook/business-ops/employee-enablement/onboarding-access-requests/#fleet-intelligence--remote-lockwipe) <!-- Fleetsmith will be deprecated for DriveStrike. When this happens, this link needs to be updated. -->
- [IT Help Team](/handbook/business-ops/employee-enablement/self-help-troubleshooting/) Policies and Standards
- [Team Member Enablement Policies and Standards](/handbook/business-ops/team-member-enablement/onboarding-access-requests/)
- [Inventory Management](/handbook/business-ops/team-member-enablement/onboarding-access-requests/#fleet-intelligence--remote-lockwipe) <!-- Fleetsmith will be deprecated for DriveStrike. When this happens, this link needs to be updated. -->
- [IT Help Team](/handbook/business-ops/team-member-enablement/self-help-troubleshooting/) Policies and Standards
- General Policies and Standards
- [Offboarding Procedures](https://about.gitlab.com/handbook/people-group/offboarding/offboarding_guidelines/)
......
......@@ -52,7 +52,7 @@ The scope of this control is broad by design. Asset inventories are the source o
Non-public information relating to this security control as well as links to the work associated with various phases of project work can be found in the [Inventory Management control issue](https://gitlab.com/gitlab-com/gl-security/compliance/compliance/issues/761).
### Policy Reference
* [Fleet Intelligence (Fleetsmith)](/handbook/business-ops/employee-enablement/onboarding-access-requests/#fleet-intelligence--remote-lockwipe)
* [Fleet Intelligence (Fleetsmith)](/handbook/business-ops/team-member-enablement/onboarding-access-requests/#fleet-intelligence--remote-lockwipe)
## Framework Mapping
* ISO
......
......@@ -23,7 +23,7 @@ We have a variety of methods for identifying and [recruiting participants for re
### Pre-requisites
1. You query the data warehouse using Structured Query Language (SQL). There are countless guides to learning SQL available for free on the Web. There are many different flavors of SQL, and the one we use is [Snowflake](https://docs.snowflake.com/en/index.html). However, most basic functionality is consistent among the major variations of SQL, so don't feel like you need to seek out Snowflake-specific resources.
1. In order to query the data warehouse, you'll need [Editor access](https://about.gitlab.com/handbook/business-ops/data-team/platform/periscope/#editor-access) to Sisense (formerly Periscope). This requires completing an [access request](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/).
1. In order to query the data warehouse, you'll need [Editor access](https://about.gitlab.com/handbook/business-ops/data-team/platform/periscope/#editor-access) to Sisense (formerly Periscope). This requires completing an [access request](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/).
1. [Data for Product Managers](https://about.gitlab.com/handbook/business-ops/data-team/programs/data-for-product-managers/) provides an overview of how the gain access to the SQL Explorer in Sisense where you will write and execute your queries, as well as providing a high level over view of how the warehouse is structured.
1. The Data team [documents individual data warehouse tables](https://dbt.gitlabdata.com/#!/overview) using a tool called dbt. Some tables are better documented and contain purpose descriptions and explanations of different columns, and some unfortunately do not. However, documentation does improve over time.
......
......@@ -25,7 +25,7 @@ The company will reimburse for the following items if you **need it for work or
The below averages are what GitLab **usually** reimburse. If you prefer to spend more on a given item, that's OK considering the average price. You may attach the receipt during expensing which shows the full purchase price. You are also welcome to expense the `GitLab Average Price in USD` portion. For example, if you purchase a high-end Steelcase ergonomic chair, you are welcome to expense the average price per the table below and cover the rest with personal funds. We are encouraging our members to use their best judgment when spending the company's money.
Team members should not use a Corporate Card to purchase office equipment for their personal workspace. All office equipment purchases for a team member's personal workspace should be made on a personal credit card and expensed. For Laptop Purchases/Refreshes, please refer to [IT Ops Laptop](/handbook/business-ops/employee-enablement/onboarding-access-requests/#laptops) policy and procedure.
Team members should not use a Corporate Card to purchase office equipment for their personal workspace. All office equipment purchases for a team member's personal workspace should be made on a personal credit card and expensed. For Laptop Purchases/Refreshes, please refer to [IT Ops Laptop](/handbook/business-ops/team-member-enablement/onboarding-access-requests/#laptops) policy and procedure.
### Setting up a home office for the first time?
......
......@@ -142,7 +142,7 @@ One person from the recruiting team (typically the [Candidate Experience Special
1. Once the new hire's profile in BambooHR is generated, The Candidate Experience Specialist will upload the signed contract and the completed background check into the BambooHR profile.
1. The Candidate Experience Specialist will send an email to total-rewards@gitlab with any variations in contract language (for example a draw). Compensation will sync with Payroll and Sales Ops for any necessary notifications on payment types.
1. The Candidate Experience Specialist will email the new team member the Welcome Email from Greenhouse with a Cc to the recruiter, IT Ops and hiring manager. For new team members in USA, use 'GitLab Welcome - US only' template. For team members located outside the US, use 'GitLab Welcome - non US' template
* Instructions on the [Notebook Ordering Process](/handbook/business-ops/employee-enablement/onboarding-access-requests/#laptops) are included with this email.
* Instructions on the [Notebook Ordering Process](/handbook/business-ops/team-member-enablement/onboarding-access-requests/#laptops) are included with this email.
1. The recruiter will unpublish the vacancy in Greenhouse for the internal job board and disposition any remaining candidates if necessary. Once complete, the recruiter will ping the Candidate Experience Specialist to close the role or close the role themselves.
1. The recruiter should create a MR on the [Careers page](/jobs/careers/) to remove the vacancy from the list. The CES should audit that this step was complete.
1. Should the start date change after the welcome email is sent please see the required steps [here](/handbook/hiring/recruiting-framework/ces-contract-processes/#how-to-update-a-start-date-after-the-contract-is-signed).
......
......@@ -180,7 +180,7 @@ The Recruiter will email the candidate and ask if they want to book a zoom call
- [Unlimited paid-time-off](https://about.gitlab.com/handbook/paid-time-off/)
- [Incentives](https://about.gitlab.com/handbook/incentives/)
- [Office equipment/reimbursements](https://about.gitlab.com/handbook/spending-company-money/)
- [Configuring your new laptop](/handbook/business-ops/employee-enablement/onboarding-access-requests/#configuring-new-laptops--apple-ids)
- [Configuring your new laptop](/handbook/business-ops/team-member-enablement/onboarding-access-requests/#configuring-new-laptops--apple-ids)
- [Employment Assistance Program](https://about.gitlab.com/handbook/benefits/#employee-assistance-program)
After the verbal offer is made the recruiter can send an email to the candidate with all the information covered in the zoom call.
......
......@@ -163,7 +163,7 @@ Please use [issues](https://gitlab.com/gitlab-com/www-gitlab-com/issues) to ask
* [Business Operations](/handbook/business-ops/)
* [Enterprise Applications](/handbook/business-ops/enterprise-applications/)
* [Data](/handbook/business-ops/data-team/)
* [Employee Enablement](/handbook/business-ops/employee-enablement/)
* [Team Member Enablement](/handbook/business-ops/team-member-enablement/)
* [Procurement](/handbook/finance/procurement/)
* [Internal Audit](/handbook/internal-audit/)
* [Sarbanes-Oxley (SOX) Compliance](/handbook/internal-audit/sarbanes-oxley/)
......
......@@ -45,7 +45,7 @@ _Typically started in first week, completed by end of second week_
1. [ ] Under your profile on Zendesk, it should read `Admin`. If it reads `Agent` or `Light Agent`, inform your manager.
1. [ ] Add a [profile picture](https://support.zendesk.com/hc/en-us/articles/203690996-Updating-your-user-profile-and-password#topic_rgk_2z2_kh) to your Zendesk account
1. [ ] [Add Facebook to one of your personal views on Zendesk](https://about.gitlab.com/handbook/marketing/community-relations/community-advocacy/tools/zendesk/#view-limits-workaround).
1. [ ] Open an [Access Request](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/)to be added as a ['Light Agent' on the Support Zendesk Instance](https://about.gitlab.com/handbook/support/internal-support/#light-agent-zendesk-accounts-available-for-all-gitlab-staff). Advocates use this instance to check in on support tickets inquired about over Twitter.
1. [ ] Open an [Access Request](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/)to be added as a ['Light Agent' on the Support Zendesk Instance](https://about.gitlab.com/handbook/support/internal-support/#light-agent-zendesk-accounts-available-for-all-gitlab-staff). Advocates use this instance to check in on support tickets inquired about over Twitter.
## Git and GitLab Basics:
......
......@@ -87,7 +87,7 @@ After the initial contact and agreeing to the subscription plan update:
### Zendesk access
Zendesk access is provided during onboarding for every Community Advocate. Access as an Agent (read/write access to tickets) or a Light Agent (read-only access to tickets) can also be provided for other team members using the [access request](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/#single-person-access-request) process if needed.
Zendesk access is provided during onboarding for every Community Advocate. Access as an Agent (read/write access to tickets) or a Light Agent (read-only access to tickets) can also be provided for other team members using the [access request](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/#single-person-access-request) process if needed.
Once access is set up:
......
......@@ -36,7 +36,7 @@ Community Advocates monitor the following:
1. Slack channels: `#education-oss`
1. Email aliases: education@gitlab.com, opensource@gitlab.com, and startups@gitlab.com.
* **In order to setup these accounts in your inbox:**
* Follow the [steps to set up the `education@gitlab.com` email alias in your inbox](/handbook/marketing/community-relations/community-advocacy/workflows/e-mail/#setting-up-aliases). If you do not have access please submit an [access request](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/).
* Follow the [steps to set up the `education@gitlab.com` email alias in your inbox](/handbook/marketing/community-relations/community-advocacy/workflows/e-mail/#setting-up-aliases). If you do not have access please submit an [access request](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/).
* Follow the [steps to set up a filter in your inbox](/handbook/tools-and-tips/#apply-label-to-all-gitlab-generated-emails) to forward all emails sent from Services@sertifi.net to community@gitlab.com. This filter is required because all notifications from eSertifi regarding action on a quote are sent to the *senders* personal email inbox. These notifications need to appear in Zendesk so proper action can be taken.
The priorities for the daily workflow are as follows:
......
......@@ -25,7 +25,7 @@ PathFactory (PF) is leveraged as our [content library & content distribution sys
## Access
The Marketing Operations team is responsible for managing access requests & provisioning the appropriate level of access for each role/function. Providing access is generally hanlded via baseline entitlement; however, if you need access and it is *not* part of your roles baseline entitlement please open a [`Single Person Access Request` issue](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/#single-person-access-request) and provide business reason why access is needed.
The Marketing Operations team is responsible for managing access requests & provisioning the appropriate level of access for each role/function. Providing access is generally hanlded via baseline entitlement; however, if you need access and it is *not* part of your roles baseline entitlement please open a [`Single Person Access Request` issue](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/#single-person-access-request) and provide business reason why access is needed.
**User Roles**
......
......@@ -166,7 +166,7 @@ In order to see the video,
## Access
1. GitLab branded channel: To request access, create a [Single Person Access Request issue](/handbook/business-ops/employee-enablement/onboarding-access-requests/access-requests/#single-person-access-request) and assign the listed provisioner (column G) from the [Tech Stack spreadsheet](https://docs.google.com/spreadsheets/d/1mTNZHsK3TWzQdeFqkITKA0pHADjuurv37XMuHv12hDU/edit#gid=0).
1. GitLab branded channel: To request access, create a [Single Person Access Request issue](/handbook/business-ops/team-member-enablement/onboarding-access-requests/access-requests/#single-person-access-request) and assign the listed provisioner (column G) from the [Tech Stack spreadsheet](https://docs.google.com/spreadsheets/d/1mTNZHsK3TWzQdeFqkITKA0pHADjuurv37XMuHv12hDU/edit#gid=0).
1. GitLab Unfiltered: Everyone should get access to YouTube Unfiltered during onboarding. If you do not see an invitation in your Inbox, please check the [Pending Invitations](https://myaccount.google.com/brandaccounts) section of your GSuite account. If your invitation is not there, please request a new invitation in the `#peopleops` Slack channel.
## Commenting
......
......@@ -25,7 +25,7 @@ GitLab-managed assets are provided to conduct GitLab business with consideration
Those receiving GitLab-provided assets are responsible for exercising good judgment when using GitLab-managed computers and accessing GitLab-managed data.
As per the [onboarding issue procedures](https://gitlab.com/gitlab-com/people-group/employment-templates-2/blob/master/.gitlab/issue_templates/onboarding.md) outlined in our handbook, evidence of device encryption and device serial number must be provided to IT Ops prior to the completion of onboarding period. All MAC laptops procured by GitLab will come configured with [JAMF](/handbook/business-ops/employee-enablement/onboarding-access-requests/endpoint-management/). GitLab team members procuring and expensing MAC Laptops will require [JAMF](/handbook/business-ops/employee-enablement/onboarding-access-requests/endpoint-management/) to be installed. Please work with IT Ops to ensure [JAMF](/handbook/business-ops/employee-enablement/onboarding-access-requests/endpoint-management/) is properly installed.
As per the [onboarding issue procedures](https://gitlab.com/gitlab-com/people-group/employment-templates-2/blob/master/.gitlab/issue_templates/onboarding.md) outlined in our handbook, evidence of device encryption and device serial number must be provided to IT Ops prior to the completion of onboarding period. All MAC laptops procured by GitLab will come configured with [JAMF](/handbook/business-ops/team-member-enablement/onboarding-access-requests/endpoint-management/). GitLab team members procuring and expensing MAC Laptops will require [JAMF](/handbook/business-ops/team-member-enablement/onboarding-access-requests/endpoint-management/) to be installed. Please work with IT Ops to ensure [JAMF](/handbook/business-ops/team-member-enablement/onboarding-access-requests/endpoint-management/) is properly installed.
### Security and Proprietary Information
......@@ -76,7 +76,7 @@ All personal mobile computing devices used to access GitLab-managed data, includ
#### Unable to Use Company Laptop
For new employees who have not received a company laptop, there are [exception processes](/handbook/business-ops/employee-enablement/onboarding-access-requests/#exception-processes) for using non-company devices.
For new employees who have not received a company laptop, there are [exception processes](/handbook/business-ops/team-member-enablement/onboarding-access-requests/#exception-processes) for using non-company devices.
The same exception processes apply in the case of a corporate laptop being unavailable due to loss, theft or disrepair. See [lost or stolen procedures](/handbook/security/#panic-email) for additional information. While the exception processes are considered a temporary solution, you still need to make sure the non-company system meets [basic configuration standards](/handbook/security/#laptop-or-desktop-system-configuration), and a Microsoft Windows system is still not allowed access under any circumstances.
......
......@@ -102,6 +102,6 @@ If you are a team member residing in India, please consider using the following
To initiate a change in name please complete the following: