Update IR links to page

1. **Be a Role Model of our [Values](/handbook/values/).**

1. **Feedback is Essential.** It is difficult to know what is appropriate in every one of our team members 60+ countries. We encourage team members to give feedback and receive feedback in a considerate way.

1. **Do not underestimate a 1:1.** Asynchronous communication (e.g., via text) is helpful and necessary. In some cases (e.g., to clarify misunderstandings) it can be much more effective to jump on a Zoom video call.

1. **Always Adhere to our [Anti-Harassment Policy](/handbook/people-group/anti-harassment/) and [GitLab Code of Business Conduct and Ethics](https://ir.gitlab.com/static-files/7d8c7eb3-cb17-4d68-a607-1b7a1fa1c95d).** Everyone should be comfortable in their work environment.

1. **Always Adhere to our [Anti-Harassment Policy](/handbook/people-group/anti-harassment/) and [GitLab Code of Business Conduct and Ethics](https://ir.gitlab.com/governance/governance-documents/default.aspx).** Everyone should be comfortable in their work environment.

1. **Focus on what we can directly influence.** There are many factors we can't directly influence and we should avoid spending time discussing those things. For example, we don't talk about our [market capitalization](/handbook/company/being-a-public-company/#market-capitalization) because aspects of this are out of our control. Instead, we should focus on how we can work together to achieve company objectives and grow [annual recurring revenue](/handbook/sales/sales-term-glossary/arr-in-practice/).

1. **Commit to [active and effective listening](/handbook/leadership/coaching/#essential-coaching-skills)**.

## What to do if you witness or are subjected to unacceptable behavior

If you experience behavior which violates this policy or [GitLab's Code of Business Conduct and Ethics](https://ir.gitlab.com/static-files/7d8c7eb3-cb17-4d68-a607-1b7a1fa1c95d), please contact the nearest member of event staff or the third party security staff, if on-site. If there is a life safety issue, please call emergency services (In the US, call 911.). The event staff can usually be identified by special badges/attire. We will appoint designated PeopleOps partners for internal company events who will be available to support in these possible reporting situations. Our policy means that we will look into and review every allegation of violation of our policy and respond appropriately. Event staff will help participants contact hotel/venue/event security or local law enforcement, provide escorts, or otherwise assist those experiencing discomfort or harassment to feel safe for the duration of the event. We value your attendance, and we want to ensure that all participants feel safe and comfortable.

If you experience behavior which violates this policy or [GitLab's Code of Business Conduct and Ethics](https://ir.gitlab.com/governance/governance-documents/default.aspx), please contact the nearest member of event staff or the third party security staff, if on-site. If there is a life safety issue, please call emergency services (In the US, call 911.). The event staff can usually be identified by special badges/attire. We will appoint designated PeopleOps partners for internal company events who will be available to support in these possible reporting situations. Our policy means that we will look into and review every allegation of violation of our policy and respond appropriately. Event staff will help participants contact hotel/venue/event security or local law enforcement, provide escorts, or otherwise assist those experiencing discomfort or harassment to feel safe for the duration of the event. We value your attendance, and we want to ensure that all participants feel safe and comfortable.

Please note: While we take all concerns raised seriously, we will use our discretion as to determining when and how to follow up on reported incidents, and may decline to take any further action and/or may direct the participant to other resources for resolution.

*“With GitLab’s second ESG Report, we demonstrate our values of iteration and transparency, sharing how we continue to build on our approach to addressing the issues that matter most to our stakeholders and our business. One key example is the launch of our AI Transparency Center, underscoring how we are leveraging the power of AI within a clear framework of ethics, responsibility, and accountability. As our innovation continues to break down barriers, we recognize the increasing opportunity of integrating our business and sustainability strategies to create value for our customers, our shareholders, our team members, and the broader community.”* –**Robin Schulman**, Chief Legal Officer, Head of Corporate Affairs, and Corporate Secretary

GitLab’s Environmental, Social, and Governance (“ESG”) Report includes information on our key ESG focus areas, our programs and policies, achievements to date, metrics and targets that help define our ESG program, and our plans for the future. Data about GitLab’s financial performance is not included in this report and may be found in our [financial and SEC filings](https://ir.gitlab.com/financial-information/sec-filings?field_nir_sec_date_filed_value=).

GitLab’s Environmental, Social, and Governance (“ESG”) Report includes information on our key ESG focus areas, our programs and policies, achievements to date, metrics and targets that help define our ESG program, and our plans for the future. Data about GitLab’s financial performance is not included in this report and may be found in our [financial and SEC filings](https://ir.gitlab.com/financials/sec-filings/default.aspx).

Unless otherwise specified, the information included in this report was last updated on July 18, 2024. The content included covers Fiscal Year 2024 (“FY24”) (as of January 31, 2024) and we plan to update the report annually. Throughout the report, there may be mentions of Fiscal Year 2025 (“FY25”), which runs from February 1, 2024, through January 31, 2025. We would also like to note that GitLab maintains a public-facing [handbook](/handbook/), pages of which are linked throughout the report. These pages are maintained separately and may reflect a different reporting period than this report.

GitLab is strongly committed to good corporate governance practices, which provide an important framework within which our [Board](https://ir.gitlab.com/corporate-governance/board-of-directors-grid) and [executive leadership](https://ir.gitlab.com/corporate-governance/executive-leadership-grid) can pursue our strategic objectives for the benefit of our shareholders.

The Board's duty is to serve as a prudent fiduciary for shareholders and to oversee the management of the company's business. To fulfill its responsibilities and discharge its duty, the Board follows the procedures and standards set forth by GitLab’s [Corporate Governance Guidelines](https://ir.gitlab.com/static-files/f108c2c0-2426-4bf5-b1db-054498136c0b) and [other governance documents](https://ir.gitlab.com/corporate-governance/documents-charters).

The Board's duty is to serve as a prudent fiduciary for shareholders and to oversee the management of the company's business. To fulfill its responsibilities and discharge its duty, the Board follows the procedures and standards set forth by GitLab’s [Corporate Governance Guidelines](https://ir.gitlab.com/governance/governance-documents/default.aspx) and [other governance documents](https://ir.gitlab.com/governance/governance-documents/default.aspx).

Board members’ responsibilities include:

#### Business Ethics

GitLab is committed to the highest standards of legal and ethical business conduct. It has long operated its business consistent with operating principles and policies that reinforce this commitment. GitLab complies with all laws and regulations that are applicable to its activities and expects all team members to adhere to our ethical standards and legal and regulatory obligations. These expectations are reflected and reinforced by our [Code of Business Conduct and Ethics](https://ir.gitlab.com/static-files/7d8c7eb3-cb17-4d68-a607-1b7a1fa1c95d?_gl=1*1ajdvmc*_ga*OTgxNjAzNjM1LjE2ODMyMDg3MTk.*_ga_ENFH3X7M5Y*MTY4NDk2MTE4MC4xMy4xLjE2ODQ5NjE3MDYuMC4wLjA.) (“Code of Conduct”) and various supporting [policies, procedures, and other resources](/handbook/legal/ethics-compliance-program/#compliance-standards-guidelines--other-resources) (collectively, “Compliance Standards”).

GitLab is committed to the highest standards of legal and ethical business conduct. It has long operated its business consistent with operating principles and policies that reinforce this commitment. GitLab complies with all laws and regulations that are applicable to its activities and expects all team members to adhere to our ethical standards and legal and regulatory obligations. These expectations are reflected and reinforced by our [Code of Business Conduct and Ethics](https://ir.gitlab.com/governance/governance-documents/default.aspx?_gl=1*1ajdvmc*_ga*OTgxNjAzNjM1LjE2ODMyMDg3MTk.*_ga_ENFH3X7M5Y*MTY4NDk2MTE4MC4xMy4xLjE2ODQ5NjE3MDYuMC4wLjA.) (“Code of Conduct”) and various supporting [policies, procedures, and other resources](/handbook/legal/ethics-compliance-program/#compliance-standards-guidelines--other-resources) (collectively, “Compliance Standards”).

In FY24, we centralized our compliance efforts. The [Ethics and Compliance Program](/handbook/legal/ethics-compliance-program/#ethics-and-compliance-program-charter), is designed to help GitLab team members maintain its culture of compliance and to promote ethical decision-making by:

## Customer acceptance

We firmly adhere to laws including trade compliance laws -- see the [GitLab Code of Business Conduct and Ethics](https://ir.gitlab.com/static-files/7d8c7eb3-cb17-4d68-a607-1b7a1fa1c95d), in countries where we do business, and welcome everyone abiding by those legal restrictions to be customers of GitLab. In some circumstances, we may opt to not work with particular organizations, on a case-by-case basis. Some reasons we may choose not to work with certain entities include, but are not limited to:

We firmly adhere to laws including trade compliance laws -- see the [GitLab Code of Business Conduct and Ethics](https://ir.gitlab.com/governance/governance-documents/default.aspx), in countries where we do business, and welcome everyone abiding by those legal restrictions to be customers of GitLab. In some circumstances, we may opt to not work with particular organizations, on a case-by-case basis. Some reasons we may choose not to work with certain entities include, but are not limited to:

1. Engaging in illegal, unlawful behavior.

1. Making derogatory statements or threats toward anyone in our community.

- Our mission is to "enable everyone to contribute to and co-create the software that powers our world." This mission is in alignment with our open source roots and the [MIT license](https://en.wikipedia.org/wiki/MIT_License) our open source software is subject to. The MIT License is a free software license that allows users the freedom to run the program as they wish, for any purpose.

- GitLab has a [contributor code of conduct](https://about.gitlab.com/community/contribute/code-of-conduct/) for *how* to contribute to GitLab, but there are no restrictions on *who* can contribute to GitLab. We desire that everyone can contribute, as long as they abide by the code of conduct.

- GitLab has a set of values for how GitLab team members strive to conduct themselves. We don't expect all companies to value collaboration, results, efficiency, diversity, inclusion and transparency in the same way we do. As an open company, "everyone can contribute" is our default and [transparency](/handbook/values/#transparency) is our check and balance. Transparency means our handbook, issues, merge requests and product roadmap are online for everyone to see and contribute to.

- Related topic: At GitLab, we want to avoid an environment where people feel alienated for their religious or political opinions. Therefore, we encourage GitLab team members to refrain from taking positions on specific [religious or political issues](/handbook/values/#religion-and-politics-at-work) in public company forums (such as on the GitLab Contribute stage or Slack channels) because it is easy to alienate people that may have a minority opinion. It is acceptable to bring up these topics in social contexts such as coffee chats and real-life meetups with other coworkers, but always be aware of cultural sensitivities, exercise your best judgment, and make sure you stay within the boundaries of our [Code of Business Conduct & Ethics](https://ir.gitlab.com/static-files/7d8c7eb3-cb17-4d68-a607-1b7a1fa1c95d). We always encourage [discussion and iteration](/handbook/values/#challenger-mindset) on any company policy, including this one.

- Related topic: At GitLab, we want to avoid an environment where people feel alienated for their religious or political opinions. Therefore, we encourage GitLab team members to refrain from taking positions on specific [religious or political issues](/handbook/values/#religion-and-politics-at-work) in public company forums (such as on the GitLab Contribute stage or Slack channels) because it is easy to alienate people that may have a minority opinion. It is acceptable to bring up these topics in social contexts such as coffee chats and real-life meetups with other coworkers, but always be aware of cultural sensitivities, exercise your best judgment, and make sure you stay within the boundaries of our [Code of Business Conduct & Ethics](https://ir.gitlab.com/governance/governance-documents/default.aspx). We always encourage [discussion and iteration](/handbook/values/#challenger-mindset) on any company policy, including this one.

## Mitigating Concerns

1. Complain up and explain down. Raise concerns you hear to your manager. When peers or reports complain, explain why a decision was made. If you don't understand why, ask your manager.

1. Create empathy for decisions from other leaders that negatively impact your team by explaining the reasons behind them. Organize a recorded AMA session with your team and the other leaders and encourage your team (as well as yourself) to ask any unanswered questions. Lead by example by ensuring that the discussion exposes what is [best for the organization as a whole](/handbook/values/#cross-functional-optimization). Never present yourself as protecting the team from the rest of the organization; this creates a [siege mentality](https://en.wikipedia.org/wiki/Siege_mentality) and hinders [collaboration](/handbook/values/#collaboration).

1. Coach team members to establish good [remote work practices](/handbook/company/culture/all-remote/), by encouraging [asynchronous communication](/handbook/company/culture/all-remote/management/#asynchronous), being [handbook-first](/handbook/about/handbook-usage/#why-handbook-first), communicating poor audio or [video quality](https://about.gitlab.com/blog/2019/08/05/tips-for-mastering-video-calls/), or pointing out an open microphone.

1. Ensuring that GitLab's policies are upheld is an essential part of a manager's responsibility. Managers have an obligation to look out for both their team members and the business's best interest. If a manager becomes aware that a team member is in violation of a GitLab policy (including *but not limited to* the [GitLab Code of Business Conduct and Ethics](https://ir.gitlab.com/static-files/7d8c7eb3-cb17-4d68-a607-1b7a1fa1c95d) and [Relocation policy](/handbook/people-group/relocation/) as examples), it is their responsibility to communicate this to the [aligned People Business Partner](/handbook/people-group/people-business-partners/#people-business-partner-alignments) or Legal team immediately.

1. Ensuring that GitLab's policies are upheld is an essential part of a manager's responsibility. Managers have an obligation to look out for both their team members and the business's best interest. If a manager becomes aware that a team member is in violation of a GitLab policy (including *but not limited to* the [GitLab Code of Business Conduct and Ethics](https://ir.gitlab.com/governance/governance-documents/default.aspx) and [Relocation policy](/handbook/people-group/relocation/) as examples), it is their responsibility to communicate this to the [aligned People Business Partner](/handbook/people-group/people-business-partners/#people-business-partner-alignments) or Legal team immediately.

#### Board Members