Merge branch 'jburrows001-update-baseline-entitlements' into 'master'

Add baseline entitlements for all GitLabbers

See merge request gitlab-com/www-gitlab-com!23137

source/handbook/business-ops/it-ops-team/index.html.md

@@ -29,24 +29,35 @@ https://gitlab.com/gitlab-com/access-requests).
 ### Baseline Entitlements
-For all incoming GitLabbers, access to systems is handled through on-boarding issues. If your on-boarding issue is complete and closed but you still need access to a system listed below, please create a [new access request issue](https://gitlab.com/gitlab-com/access-requests/issues/new) and add a link to this page in lieu of manager approval:
-#### Systems that all GitLabbers should have access to
-| System Name | Business Purpose | Approved Role | [Data Classification](https://about.gitlab.com/handbook/engineering/security/data-classification-policy.html) |
+For all incoming team-members, access to systems is handled through on-boarding issues. If your on-boarding issue is complete and closed but you still need access to a system listed below, please create a [new access request issue](https://gitlab.com/gitlab-com/access-requests/issues/new) and add a link to this page in lieu of manager approval:
+#### Systems that all team-members should have access to
+100% of team-members should have access to the following systems at the following levels of access as part of their work at GitLab. This list has been pre-approved so if any team-member needs access to these systems they can reach out directly to the [system admin(s)](https://about.gitlab.com/handbook/business-ops/#tech-stack) and request access based on this pre-approval.
+
+| System Name | Business Purpose | System Role (What level of access) | [Data Classification](https://about.gitlab.com/handbook/engineering/security/data-classification-policy.html) |
 |---|---|---|---|
 | 1Password | User Password Management | Team Member | RED |
+| BambooHR | Human Resource Platform | Employee | RED |
+| Calendly | Add-in for meeting Scheduling | Employee | YELLOW |
+| Carta | Shares Management | Employee | RED |
+| CultureAmp | 360 Feedback Management | User | YELLOW |
 | Expensify | Expense Claims and Management | Employee | ORANGE |
+| GitLab.com | Gitlab Application for Staff | Employee | RED |
 | Greenhouse | Recruiting Portal | Interviewer | RED |
+| Gsuite | Email, Calendar, and Document sharing/collaboration | GitLab.com Org Unit | RED |
 | Moo | Business Cards | User | YELLOW |
 | NexTravel | Travel booking | Employee | ORANGE |
-| Periscope | Data Visualization | View | ORANGE |
 | Sertifi | Digital signatures, payments, and authorizations | User | YELLOW |
+| Slack | GitLab async communications | Member | RED |
+| Periscope Data | Data Analysis and Visualisation | User | RED |
+| Will Learning | Staff Training and Awareness Portal | User | YELLOW |
 | Zoom | For video conferencing / meetings | User | RED |
+
 ## Automated Group Membership Reports for Managers
-If you would like to check whether or not a GitLabber is a member of a Slack or a G-Suite group, you can view the following automated group membership reports:
+If you would like to check whether or not a team-member is a member of a Slack or a G-Suite group, you can view the following automated group membership reports:
 [G-Suite Group Membership Reports](https://gitlab.com/gitlab-com/security-tools/report-gsuite-group-members)
@@ -74,23 +85,23 @@ Screenshots and videos are very helpful when experiencing an issue, especially i
 ### New Laptops
-Laptops are purchased by IT Ops when a GitLabber comes on board; the GitLabber will be sent a form to fill out for ordering.
+Laptops are purchased by IT Ops when a team-member comes on board; the team-member will be sent a form to fill out for ordering.
 ### Laptop Refresh
 Replacement laptops for broken GitLab laptops can be purchased as needed by [creating an issue](https://gitlab.com/gitlab-com/business-ops/itops/issue-tracker/issues/new?issue) in the IT Ops issue tracker project and using the `repair_replace` 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](https://about.gitlab.com/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 employees, but GitLabbers become eligible for an updated laptop after 3 years.
+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](https://about.gitlab.com/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.
 ### Configuring New Laptops
-New laptops should be configured with security in mind. Please refer to [security best practices](https://about.gitlab.com/handbook/security/#best-practices) when configuring new laptops. **All GitLabbers must provide proof of whole-disk encryption within the new laptop order issue.**
+New laptops should be configured with security in mind. Please refer to [security best practices](https://about.gitlab.com/handbook/security/#best-practices) when configuring new laptops. **All team-members must provide proof of whole-disk encryption within the new laptop order issue.**
 ### Returning Old Laptops
-Part of the IT Ops replacement laptop process is providing each GitLabber with instructions about how to return their old laptop (whether outdated or broken). All laptops must be returned **within 2 weeks of receiving the replacement laptop**, so please prioritize transferring information between laptops within this timeframe.
-All GitLabber laptops must be securely erased before being returned. This not only protects the company, but also protects you since it is possible for personal information to exist on these machines. Reformatting a computer is not sufficient in these cases because it is possible for sensitive data to be recovered after reinstalling an operating system.
+Part of the IT Ops replacement laptop process is providing each team-member with instructions about how to return their old laptop (whether outdated or broken). All laptops must be returned **within 2 weeks of receiving the replacement laptop**, so please prioritize transferring information between laptops within this timeframe.
+All team-member laptops must be securely erased before being returned. This not only protects the company, but also protects you since it is possible for personal information to exist on these machines. Reformatting a computer is not sufficient in these cases because it is possible for sensitive data to be recovered after reinstalling an operating system.
 ## Other Resources