diff --git a/CODEOWNERS b/CODEOWNERS
new file mode 100644
index 0000000000..f467f74f93
--- /dev/null
+++ b/CODEOWNERS
@@ -0,0 +1 @@
+* @joel-rieke @meghan-bailey @mkrty @JoshuaAtTrimble
diff --git a/CODE_OF_CONDUCT.MD b/CODE_OF_CONDUCT.MD
new file mode 100644
index 0000000000..b7797e28a8
--- /dev/null
+++ b/CODE_OF_CONDUCT.MD
@@ -0,0 +1,41 @@
+
+## Code of conduct ✒
+
+### Our Pledge ⌗
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project
+ and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+
+### Our Standards ®
+Examples of behaviour that contributes to **creating a positive environment** include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints
+- Gracefully accepting constructive criticism and feedback
+- Focusing on what is best for the community
+
+Examples of **unacceptable** behaviour by participants include:
+
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Publishing others' private information, such as a physical or electronic address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+### Our Responsibilities ✓
+
+Project maintainers are responsible for clarifying the standards of acceptable behaviour and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behaviour.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviours that they deem inappropriate, threatening, offensive, or harmful.
+
+### Scope ⌚
+
+This **Code of Conduct** applies within project spaces when an individual is representing the project or its community. 
+Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. 
+Representation of a project may be further defined and clarified by project maintainers.
+
+### Enforcement ⚠
+
+Instances of abusive, harassing, or otherwise unacceptable behaviour may be reported by contacting the project team. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+
diff --git a/SECURITY.md b/SECURITY.md
new file mode 100644
index 0000000000..988fb94c0c
--- /dev/null
+++ b/SECURITY.md
@@ -0,0 +1,17 @@
+# Security Policy
+
+## Reporting a Vulnerability
+
+Report security vulnerabilities by emailing the Trimble Cybersecurity team at:
+
+    cybersecurity@trimble.com
+
+Report security vulnerabilities in third-party modules to the person or team maintaining the module.
+
+## Disclosure Policy
+
+When the security team receives a security bug report, they will assign it to a primary handler. This person will coordinate the fix and release process, involving the following steps:
+
+- Confirm the problem and determine the affected versions.
+- Audit code to find any potential similar problems.
+- Prepare fixes for all releases still under maintenance. These fixes will be released as fast as possible.
\ No newline at end of file