@@ -56,7 +56,7 @@ The [Sustainability](/handbook/legal/esg/) team drives and integrates GitLab's r
For quick questions that **do not** require legal advice, deliverables, or any discussion of confidential information, you can reach out to LACA in Slack at [#legal](https://gitlab.slack.com/archives/legal). We find this channel best for questions about process, who handles what, or how to find certain things if the handbook has not yielded the right result for you after searching. #legal is not a private channel, so your inquiry will be visible to the entire company. One of our team members will do their best to answer your question in a timely fashion.
Most questions regarding specific customers require a legal case in Salesforce. Follow the process [here](/handbook/legal/customer-negotiations/#how-to-reach-the-legal-commercial-team) to open one.
Most questions regarding specific customers require a legal case in Salesforce. Follow the process [here](/handbook/legal/customer-negotiations/#how-to-reach-commercial-legal) to open one.
For other questions related to deliverables and non-sensitive information, create an issue in the [Legal and Compliance project](https://gitlab.com/gitlab-com/legal-and-compliance/-/issues). Be sure to use the template most suited to your request to engage the right team members.
description:This resource provides assistance to the GitLab Sales Team on operational and educational elements of working with GitLab Legal for Customer negotiations
---
The purpose of this Handbook resource is to provide all GitLab team members with a clear path in navigating any type of go-to-market Legal Commercial requests or processes. The information below is intended to help you to find and access certain information on your own, as well as clearly establish how to best connect with, and coordinate assistance from, the GitLab Commercial Legal team.
The purpose of this Handbook resource is to provide all GitLab team members with a clear path in navigating any type of go-to-market Commercial Legal requests or processes. The information below is intended to help you to find and access certain information on your own, as well as clearly establish how to best connect with, and coordinate assistance from, the GitLab Commercial Legal team.
Note: All references to 'GitLab Legal' or 'Legal' within this Handbook page refers to the Commercial Legal team.
@@ -15,8 +15,8 @@ The information contained on this page is organized into two distinct categories
| OPERATIONAL | EDUCATIONAL |
| ------ | ------ |
| [**How to Reach the Legal Commercial Team**](#how-to-reach-the-legal-commercial-team) | [**Overview of GitLab Agreements**](#overview-of-gitlab-agreements) |
| [**How do I get an Agreement signed**](#how-do-i-get-an-agreement-signed)(including NDAs, DPAs and Letters of Authorization) | [**When does GitLab negotiate**](#when-does-gitlab-negotiate) |
| [**How to Reach Commercial Legal**](#how-to-reach-commercial-legal) | [**Overview of GitLab Agreements**](#overview-of-gitlab-agreements) |
| [**How to Get an Agreement Signed**](#how-to-get-an-agreement-signed)(including NDAs, DPAs and Letters of Authorization) | [**When does GitLab negotiate**](#when-does-gitlab-negotiate) |
| [**Clearing Export Review in SFDC**](#export-review-in-sfdc) | [**What is Open Source Software?**](#what-is-open-source) |
| [**Requests for GitLab Financial Information and Insurance Certificates**](#requests-for-gitlab-financial-information-and-insurance-certificates) | [**Business Associate Agreements**](#business-associate-agreements-baas) |
@@ -31,44 +31,50 @@ The information contained on this page is organized into two distinct categories
## OPERATIONAL
### How to Reach the Legal Commercial Team
### How to Reach Commercial Legal
**Different situations require different approaches. In the vast majority of cases regarding revenue-related requests, the proper way to engage the Legal team is through Salesforce (SFDC) by creating a legal case per the process below.**
**Different situations require different approaches. In the vast majority of cases regarding revenue-related requests, the proper way to engage the Legal team is through Salesforce (SFDC) by creating a Legal Case or Ironclad workflow per the process below.**
1. To create a Legal Case, select the "Request Support" button in the drop down menu at the upper right corner of the customer Opportunity in SFDC and then select "Legal" from the next drop down menu. **If an opportunity does not exist, please open a $0 opportunity and follow the steps set out in this section.**
2. Once the Legal Case is correctly created, the request is logged in a queue where the appropriate Legal team member will assign themselves to the case and communicate with the requestor as applicable.
3. Step-by-step directions on opening a Legal Case:
- Select "Request Support" located at the top of your Opportunity in SFDC.
- Select "Legal" in the drop down menu that appears after you select "Request Support"
- Choose the most appropriate answers for each field (i.e., "Type of Legal Request" and "Summary of Actions"), add all relevant details in the "Next Steps" section, and upload any related document, then hit "Submit". **Please add as many details as possible and include urgency of the request or deadline, as this will allow the Legal team member to plan and prioritize accordingly.**
- Once properly submitted, a new Legal Case will be added to the Legal team's queue and the appropriate team member will assign the Legal acse to themselves to assist you.
- You will also receive an automated message via email as well as in the Chatter section of your newly created Legal Case, which will, depending on the Legal Request type, outline what documents and/or information the legal team needs to assist you. Alternatively, you may be pointed to resources that might answer your query directly. Please review this message and make sure that all necessary information is provided, and documents are attached.
- If your request involves an **NDA or MSA**, follow the process for [initiating an **Ironclad workflow**](https://docs.google.com/document/d/12UcfqG7Pnt2NbrjwF7OwxSxsyersFINem_qtb3BkOgw/edit?usp=sharing). Note the self-service options available to expedite signature.
- NDAs and MSAs were Phase 1 of an Ironclad rollout that will eventually include all template types.
2. Once the Legal Case or Ironclad workflow is correctly created, the request is logged in a queue where the appropriate Legal team member will assign themselves to the case and communicate with the requestor as applicable.
#### Step-by-step directions for opening a Legal Case
1. Select "Request Support" located at the top of your Opportunity in SFDC.
1. Select "Legal" in the drop down menu that appears after you select "Request Support"
1. Choose the most appropriate answers for each field (i.e., "Type of Legal Request" and "Summary of Actions"), add all relevant details in the "Next Steps" section, and upload any related document, then hit "Submit". **Please add as many details as possible and include urgency of the request or deadline, as this will allow the Legal team member to plan and prioritize accordingly.**
1. Once properly submitted, a new Legal Case will be added to the Legal team's queue and the appropriate team member will assign the Legal acse to themselves to assist you.
1. You will also receive an automated message via email as well as in the Chatter section of your newly created Legal Case, which will, depending on the Legal Request type, outline what documents and/or information the legal team needs to assist you. Alternatively, you may be pointed to resources that might answer your query directly. Please review this message and make sure that all necessary information is provided, and documents are attached.
- The Legal Case will be reviewed, answered and the requestor will be @ mentioned.
- Once the request is addressed, the Legal Case will be closed by the legal team member.
4. If you experience any issues opening a Legal Case, please reach out to #legal in Slack for assistance.
5. Do not tag @Legal in SFDC as the entire team gets unnecessarily notified.
6. All agreements or documents for a customer's particular opportunity should be attached in the same Legal Case: e.g. a customer returns redlines to both the Subscription Agreement and their order form, both should be uploaded to the same Legal Case.
**Reminder: Only one SFDC Legal Case should be opened for each opportunity.**
1. If you experience any issues opening a Legal Case, please reach out to #legal in Slack for assistance.
1. Do not tag @Legal in SFDC as the entire team gets unnecessarily notified.
1. All agreements or documents for a customer's particular Opportunity should be attached in the same Legal Case (e.g., a customer returns redlines to both the subscription agreement and their order form, both should be uploaded to the same Legal Case).
### How do I get an Agreement Signed
**Reminder: Only one SFDC Legal Case should be opened for each Opportunity.**
1. No one in the Sales organization is authorized to sign any agreements. Only certain individuals may execute on behalf of GitLab, see Authorization Matrix [here](https://internal.gitlab.com/handbook/company/authorization-matrix/)(as updated from time to time). If you have any questions, please reach out to the Legal team member who has been assisting with the applicable request.
1. All agreements require a Legal approval stamp in order to be signed. This stamp is placed on the agreement by a Legal team member when an executable version is reached.
### How to Get an Agreement Signed
**NOTE - the Legal Stamp is not a signature**
1. No one in the Sales organization is authorized to sign any agreement. Only certain individuals may execute on behalf of GitLab. See the Authorization Matrix [here](https://internal.gitlab.com/handbook/company/authorization-matrix/)(as updated from time to time). If you have any questions, please reach out to the Legal team member who has been assisting with the applicable request.
1. All agreements require Legal approval on the document in order to be signed. This happens one of two ways:
- A stamp is placed on the agreement by a Legal team member when an executable version is reached.
- If the agreement was processed in Ironclad, the Legal team member who approved is first in the signature workflow to apply their initials.
-**NOTE: the Legal stamp is not a signature**
1. Once the Agreement has been stamped by Legal, follow the [DocuSign Process](/handbook/sales/field-operations/order-processing/#how-to-send-an-order-form-to-the-customer-for-signature-via-docusign) to send the agreement for signature within SFDC.
1. All Sales Team Members have DocuSign access, please work with Sales Ops for any questions on how to use it. **Please be sure to copy the applicable Legal team member for all fully executed agreements**
1. All Sales Team Members have DocuSign access. Please work with Sales Ops for any questions on how to use it. **Please be sure to copy the applicable Legal team member for all fully executed agreements**
Need an NDA signed? Follow the process for [Team Members with DocuSign access](/handbook/legal/nda/).
{.h3}
#### Non-Disclosure Agreement (NDA)
### How to Get a Data Processing Addendum (DPA) Signed
Follow the steps in the [Ironclad Process Guide for Requesters](https://docs.google.com/document/d/12UcfqG7Pnt2NbrjwF7OwxSxsyersFINem_qtb3BkOgw/edit?usp=sharing).
#### Data Processing Addendum (DPA)
GitLab includes a signed version of the DPA on the Terms of Use website. As stated within the Subscription Agreement, this DPA is applicable to all customers and does not need to be countersigned. In addition, as stated within the header of the DPA, a customer's acceptance of the Subscription Agreement shall be treated as its agreement to the DPA.
### Letters of Authorization (LOA)
#### Letters of Authorization (LOA)
Visit the [Partner Operations page](/handbook/sales/field-operations/channel-operations/#letters-of-authorization) to learn how partners can request a Letter of Authorization.
@@ -129,12 +135,11 @@ Occasionally GitLab will receive a notice from a customer or partner outlining e
3. Legal confirms whether name change OR change in control:
a. For **name changes only**, Customer provides financial documentation, W9 or W8BEN to Sales/Channels.
- Sales/Ecosystems uploads documentation to SFDC.
- Legal will review the provided documentation, and if necessary, draft an Amendment to document the name change.
- Legal will provide to Sales/Ecosystems for Customer’s/partner’s review and execution.
- Legal will provide to Sales/Ecosystems for Customer's/partner's review and execution.
- Sales/Ecosystems Ops updates the applicable information in SFDC.
- Legal, upon confirming Sales/Ecosystems Op’s work is complete, closes the legal case.
- Legal, upon confirming Sales/Ecosystems Op's work is complete, closes the legal case.
4. For **change of control**, Legal confirms transaction category (acquisition, divestiture, asset sale, merger, insolvency).
@@ -142,7 +147,7 @@ Occasionally GitLab will receive a notice from a customer or partner outlining e
- Legal will draft the appropriate transfer document and will provide to Sales to send to Customer/partner.
- Customer/partner provides signed consent documentation to Sales/Ecosystems.
- Sales/Ecosystems Ops updates the applicable information in SFDC.
- Legal, upon confirming Sales/Ecosystems Op’s work is complete, closes the legal case.
- Legal, upon confirming Sales/Ecosystems Op's work is complete, closes the legal case.
@@ -84,7 +84,7 @@ Use of competitors' services: [Guidelines](https://internal.gitlab.com/handbook/
## Requesting a Certificate of Insurance
- To request a COI, please use your existing procurement request and tag the Legal Team member assigned (if applicable), or not active request exist, open an issue in the Legal and Compliance project using the [general legal template](https://gitlab.com/gitlab-com/legal-and-compliance/-/issues/new?issuable_template=general-legal-template&_gl=1*1aumr6r*_ga*MTc1Mjg0Mzg3NS4xNjc1NzE0NjA5*_ga_ENFH3X7M5Y*MTY3NjQ4OTU3Ny4xMC4xLjE2NzY0ODk2ODkuMC4wLjA). Be sure to apply the `legal-procurement::to do` label and tag `@dcolesjr`, `@chilling32`, and `@ndjohnson` in your request.
- For requests related to a customer or partner, open a [Legal Request](/handbook/legal/customer-negotiations/#how-to-reach-the-legal-commercial-team) in SFDC.
- For requests related to a customer or partner, open a [Legal Request](/handbook/legal/customer-negotiations/#how-to-reach-commercial-legal) in SFDC.
