Limit the scope of GitLab's access to team member property

Why is this change being made?

I'd like to propose this change to the expectation of privacy that GitLab team members can have regarding their own personal property. While it's common for employees to use their personal devices for business (Slack, email, etc.) and GitLab expects to have access to information concerning the business, I haven't seen a clear reason for team members to expect that the entirety of their devices become subject to company access because it was used to communicate with a coworker.

This change would make it clearer to me that GitLab maintains their right to access all communication and information on GitLab-related systems, regardless of the device that the communication happened to originate on, and that the company's interest is in work-related, not personal, information.

Author Checklist

• Correct MR template applied (e.g blog post)
• Provided a concise title for the MR
• Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
• Assign this change to the correct DRI
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
  • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.

For help with failing pipelines reach out in #mr-buddies in Slack

Edit Employee -> Team Member