diff --git a/lessons/best-practices/collaboration-etiquette.md b/lessons/best-practices/collaboration-etiquette.md
index 34a0331..9bad6d1 100644
--- a/lessons/best-practices/collaboration-etiquette.md
+++ b/lessons/best-practices/collaboration-etiquette.md
@@ -82,6 +82,8 @@ for working on a collaborative project.
 
 1. Don't hardcode model configuration values; use a configuration file in a plain text format like cfg, yaml, or toml, and read in the values.
 
+1. You don't need an upstream remote when you own a repository. If your team or organization owns a repository, an upstream remote may not be necessary (depending on org rules or practices), but it may still be a good idea.
+
 1. Avoid including data (input or output) in a source code repository. There's some gray area for data
   used in an example, but the data should be small.